Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocate WordPress site running Age Gate ≤1.0
-
DeliveryPOST payload to standalone admin.php
-
ExploitInject PHP via width/height parameter
-
ExecutionCode written to included file and executed
-
ImpactFull server compromise as web user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions - remote unauthenticated exploitation against default configurations of the AGE-GATE WordPress plugin (all versions up to and including 1.0). The standalone admin.php endpoint deliberately does not bootstrap WordPress and has no ABSPATH guard, so the registered capability/nonce arguments are decorative and provide no protection. The only prerequisites are that the vulnerable plugin is installed/active and that admin.php is directly reachable over HTTP; the capability checks advertised via the plugin's simulated menu API do NOT limit exploitation because that code path never runs for direct requests. |
| Impact | All available signals point to maximum real-world risk if the plugin is present. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity attack requiring no privileges and no user interaction, yielding full confidentiality, integrity, and availability impact (C:H/I:H/A:H) for a 9.8 CRITICAL score. The description independently corroborates this: admin.php is a standalone endpoint that does not load WordPress, carries no ABSPATH guard, and injects unsanitized POST parameters into generated PHP written to an included file - so the 'unauthenticated' claim is consistent with PR:N rather than merely inferred from text. No EPSS score, CISA KEV listing, POC reference, or SSVC decision data was provided in the input, so there is no confirmation of in-the-wild or automated exploitation; by the precision rules this is 'no public exploit identified at time of analysis.' The absence of exploitation telemetry does NOT lower the technical severity - unauthenticated RCE with no preconditions is trivially weaponizable and should be treated as a top-priority patch, with the only genuine mitigating factor being how widely this specific plugin is actually deployed. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted HTTP POST request directly to the plugin's standalone admin.php endpoint, supplying a malicious payload in the 'width' (and 'height') parameter. Because the endpoint performs no authentication, capability, or nonce checks and writes the parameter straight into generated PHP source in an included file, the injected code executes on the server. No public exploit was identified in the provided data, but the attack is low-complexity and requires no privileges or user interaction per the CVSS vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Unauthenticated remote code execution affects the AGE-GATE (wp-site-age-gate) plugin for WordPress in all versions up to and including 1.0. Because the plugin ships a standalone admin.php endpoint that never bootstraps WordPress and carries no ABSPATH guard, the capability and nonce arguments registered through the plugin's simulated menu API are purely decorative, and POST parameters such as width and height are written unsanitized into generated PHP source that is subsequently included - letting any remote attacker who can reach admin.php execute arbitrary code on the server. The vendor CVSS is 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), and no public exploit code has been identified at time of analysis; exploitation requires only that the vulnerable plugin be installed and active and that admin.php be directly reachable over HTTP.
RemediationAI
No vendor-released patch identified at time of analysis, and no fixed version number is available in the supplied data, so the safest immediate action is to deactivate and delete the AGE-GATE plugin (wp-site-age-gate) until an updated release is published; simply deactivating without removing the files may leave admin.php readable and directly requestable depending on server configuration, so deletion is preferred and its only cost is loss of the age-verification gate. If the site must keep the plugin online, block direct HTTP access to the vulnerable endpoint at the web-server or WAF layer - deny or return 403 for requests matching wp-content/plugins/wp-site-age-gate/admin.php (and consider denying direct execution of PHP files in that plugin directory generally) - but note as a trade-off that this only mitigates the standalone-endpoint entry point and does not repair the underlying unsanitized write-and-include logic, so any other path reaching the same parameters remains exploitable. Additional compensating controls are to restrict access to the plugin directory by source IP where administrative use is limited, and to deploy virtual patching rules that reject POST bodies containing PHP open tags or suspicious content in width/height parameters, with the caveat that string-matching rules of this type are easily bypassed and should be treated as temporary. Monitor the WordPress plugin Trac repository and the Wordfence threat-intel advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/05db28b4-a3de-402d-bc5b-06d5347d6724 for a patched release, and until then review web logs for direct requests to admin.php from untrusted sources as a possible indicator of exploitation.
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
The AGE-GATE plugin implements its settings interface through a self-contained admin.php file that deliberately does not load WordPress core, so none of the usual plugin-side security scaffolding is present: there is no ABSPATH guard, no nonce verification, and no functioning current_user_can() check, because the capability arguments passed to the plugin's simulated menu-registration API are never consumed on the direct-request code path. The relevant logic lives in the trunk files main.php (notably around lines 213, 279, 291 and 325), agegate.php (line 161) and nonwp.php (line 20), where request parameters such as width and height are interpolated straight into PHP source that is written to a file and then included by the application. That write-then-include pattern is the second half of the RCE chain and is why the record is classified under CWE-434 (unrestricted upload of a file with a dangerous type) even though the immediate primitive is unsanitized input concatenated into executable code - the attacker effectively controls the content of a PHP file that the server later evaluates. The CPE cpe:2.3:a:streetforce1:age-gate:*:*:*:*:*:*:*:* confirms the affected package is streetforce1/AGE-GATE as distributed through the WordPress plugin directory under the slug wp-site-age-gate, and the CVSS vector PR:N/UI:N confirms no authentication or user interaction is required.
Know when PHP 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:N/UI:N/S:U/C:H/I:H/A:H
Standalone admin.php is a direct network entry point with no auth/capability/nonce checks, giving PR:N/UI:N/AC:L, and unauthenticated RCE yields full C/I/A impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The AGE-GATE plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.0 via the 'width (and height)' parameter parameter. This is due to missing authentication, capability checks, and nonce verification on the standalone admin.php endpoint, combined with unsanitized injection of POST parameters directly into generated PHP source written to an included file. This makes it possible for unauthenticated attackers to execute code on the server. This is possible because admin.php does not load WordPress and carries no ABSPATH guard, making it a fully unauthenticated entry point regardless of the decorative capability arguments registered via the plugin's simulated menu API.
Executive ViewAI
The AGE-GATE (wp-site-age-gate) WordPress plugin, in all versions up to and including 1.0, exposes affected organizations to a critical unauthenticated remote code execution vulnerability that can lead to complete server compromise. No vendor-released patch identified at time of analysis, and no public exploit identified at time of analysis, so the primary risk is opportunistic or targeted compromise of public-facing WordPress sites that have the plugin installed and active. Leadership should treat this as an urgent containment issue for any web property running the plugin, given the potential for data loss, service disruption, and downstream reputational harm.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the AGE-GATE (wp-site-age-gate) plugin; if it must stay active, block direct HTTP access to wp-content/plugins/wp-site-age-gate/admin.php, restrict the endpoint by IP allowlist, and disable direct PHP execution in the plugin directory; deploy virtual patching or WAF rules to block suspicious POST requests to admin.php; enable file integrity monitoring and webshell scanning; monitor web and PHP logs for exploitation attempts; and rotate credentials if compromise is suspected.
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.
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-100785
GHSA-rh8j-h273-hvj3
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB