LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69138: WordPress Genemy theme <= 1.6.6 - Privilege Escalation vulnerability

Subscriber Privilege Escalation in Genemy <= 1.6.6 versions.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A low-privileged WordPress user, such as a Subscriber, may be able to gain higher privileges on sites using the Genemy theme version 1.6.6 or earlier. For affected public sites, this can put site content, configuration, and user data at risk.

Executive priority

Treat this as a near-term remediation item for any public WordPress site using Genemy. Prioritize sites with customer accounts, open registration, or business-critical content.

Technical view

CVE-2025-69138 is a high-severity privilege escalation issue in Jthemes Genemy for WordPress, reported for versions <= 1.6.6. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating network reachability, low complexity, and required low-privileged authentication.

Likely exposure

Exposure is most likely on WordPress sites running Genemy <= 1.6.6 with user registration enabled or untrusted Subscriber-level accounts. Sites without low-privileged users have reduced practical exposure, but compromised accounts may still matter.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The risk remains serious because the vulnerability requires only low-privileged authentication and can affect confidentiality, integrity, and availability.

Researcher notes

The source bundle provides limited technical detail beyond privilege escalation classification, affected theme/version statement, CWE-266, and CVSS. Do not assume exploit mechanics, vulnerable functions, or patch availability without vendor or Patchstack detail.

Mitigation direction

  • Inventory WordPress sites using the Genemy theme.
  • Check whether Genemy is version 1.6.6 or earlier.
  • Review Patchstack and vendor guidance for a fixed release.
  • Apply the vendor fix when available.
  • Restrict public registration and remove unnecessary Subscriber accounts.
  • Consider replacing the theme if no fix is available.

Validation and detection

  • Confirm installed theme name and version in WordPress.
  • Review whether public user registration is enabled.
  • Audit low-privileged accounts for unknown or stale users.
  • Check admin-user changes after June 17, 2026.
  • Monitor WordPress logs for suspicious authenticated activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-266: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-69138 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-69138Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
JthemesGenemygenemy, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-266 · source CWE mapping

Incorrect Privilege Assignment

Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.