Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain subscriber account on target site
-
DeliveryAuthenticate via WordPress login
-
ExploitIdentify unprotected theme AJAX or REST endpoint
-
ExecutionSend crafted authenticated request bypassing capability check
-
ImpactExecute unauthorized high-integrity write action (modify content or settings)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to hold at minimum a WordPress subscriber-level account on the target site, confirmed by PR:L in the CVSS vector - this is the lowest registered user role and can be obtained via self-registration if the site permits it. The site must have the Genemy theme installed and active at version 1.6.6 or earlier. The specific theme function, AJAX action name, or REST route containing the missing authorization check is not disclosed in the available data, so the precise triggering endpoint is not independently confirmed. Exploitation is limited by the authentication prerequisite: sites that disable open user registration substantially reduce exposure, as the attacker must already possess or be able to create a site account. No non-default WordPress configuration beyond having the vulnerable theme active is required. |
| Impact | The CVSS 3.1 score of 6.5 (Medium) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N reflects a network-exploitable, low-complexity flaw requiring only subscriber-level authentication. The High integrity impact (I:H) indicates the attacker can make significant unauthorized modifications - likely to theme settings, post content, or site options - while the absence of confidentiality (C:N) and availability (A:N) impact limits damage to integrity-based abuse. No EPSS data was included in the provided intelligence; no KEV listing exists and no public exploit or proof-of-concept has been identified, which collectively suggest this has not been observed in active opportunistic exploitation campaigns at time of analysis. The authentication prerequisite (PR:L) materially reduces the realistic attack surface versus unauthenticated flaws: sites that disable open user registration or enforce invitation-only account creation are substantially less exposed. The risk is real but context-dependent - a site with open registration and Genemy ≤1.6.6 active faces meaningful unauthorized modification risk; a closed-membership site faces lower residual risk. |
| Exploit ScenarioDerived | An attacker registers a free subscriber account on a WordPress site running Genemy 1.6.6 or earlier with open user registration enabled. After authenticating, the attacker crafts direct HTTP POST requests to the theme's unprotected AJAX handler or REST endpoint - invoking privileged functionality such as modifying theme options, overwriting page content, or altering site configuration - receiving a successful response because no capability check gates the action. No public exploit code has been identified at time of analysis, but the low complexity and standard WordPress attack surface make manual exploitation straightforward for any attacker familiar with WordPress theme internals. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 17, 2026
Broken access control in the Genemy WordPress theme (versions ≤1.6.6) permits subscriber-level authenticated users to perform high-integrity write operations that are supposed to be restricted to higher-privileged roles such as editor or administrator. The flaw originates from missing authorization checks (CWE-862) on theme-registered functionality, meaning the theme does not verify whether the requesting user holds sufficient WordPress capabilities before executing privileged actions. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the CVSS integrity impact rating of High and low attack complexity signal meaningful unauthorized content or configuration modification potential for any attacker able to obtain a subscriber account.
RemediationAI
Update the Genemy theme to the latest version available in the WordPress theme repository or from jthemes directly, as all releases at or below 1.6.6 are confirmed vulnerable; the exact patched version number is not independently confirmed from the available data, so administrators should verify the current release from the Patchstack advisory at https://patchstack.com/database/wordpress/theme/genemy/vulnerability/wordpress-genemy-theme-1-6-6-broken-access-control-vulnerability before upgrading. As a compensating control, disable open user registration on the WordPress site (Settings → General → uncheck 'Anyone can register') to eliminate the subscriber account creation path that enables exploitation - note this prevents legitimate self-service signups as a trade-off. Additionally, deploy a WordPress security plugin such as Wordfence or a web application firewall rule that restricts unanticipated AJAX and REST API calls from subscriber-role sessions until a confirmed patched version is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Genemy is a commercial WordPress theme developed by jthemes (CPE: cpe:2.3:a:jthemes:genemy:*:*:*:*:*:*:*:*). The root cause is CWE-862 (Missing Authorization): one or more of the theme's AJAX handlers, REST API endpoints, or admin-facing hooks does not call the appropriate WordPress capability check (e.g., current_user_can()) before executing a privileged operation. In WordPress's role hierarchy, 'subscriber' is the lowest registered user role and is granted only read access by default. A properly implemented theme must gate any write or administrative function behind an explicit capability assertion. The absence of that check collapses the privilege boundary between subscriber and higher roles, allowing low-privileged users to invoke functionality intended for editors or administrators.
Know when Genemy gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
PR:L reflects mandatory subscriber authentication; I:H captures unauthorized write capability; C:N and A:N because no data exfiltration or service disruption is indicated.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Broken Access Control in Genemy <= 1.6.6 versions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2025-210205
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB