CVE-2025-11855: age-restriction (WordPress plugin) · Improper Privilege Management
Affects age-restriction (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| age-restriction | Affected
| Fixed in– |
AI-suggested
Until an official patch is released, organizations should take immediate steps to reduce risk. First, restrict or disable user registrations or limit them to trusted users only. Review and audit all user accounts for suspicious or unauthorized administrator accounts. Temporarily disable or uninstall the age-restriction plugin if feasible. Implement strict monitoring and alerting for new administrator account creations and unusual privilege escalations. Employ Web Application Firewalls (WAFs) with custom rules to block requests to the vulnerable function or suspicious POST requests related to the plugin. Harden WordPress installations by enforcing strong authentication mechanisms such as multi-factor authentication (MFA) for all administrator accounts. Regularly back up site data and configurations to enable rapid recovery if compromise occurs. Stay informed on vendor updates and apply patches immediately once available. Consider isolating critical WordPress instances behind VPNs or IP whitelisting to limit access to authenticated users only. Conduct penetration testing focused on privilege escalation vectors to identify any other weaknesses.
Description
The age-restriction WordPress plugin through 3.0.2 does not have authorisation in the age_restrictionRemoteSupportRequest function, allowing any authenticated users, such as subscriber to create an admin user with a hardcoded username and arbitrary password.