VulnerabilityPublished 31 Oct 2025Updated 9 Jan 2026

CVE-2025-11191: RealPress (WordPress plugin) · Missing Authorization

Affects RealPress (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
RealPress	Affected =0	Fixed in–

AI-suggested

Upgrade the RealPress WordPress plugin to version 1.1.0 or later as soon as the patch is released to ensure proper authorization checks are enforced on REST API routes.
Until an official patch is available, implement custom permission checks on the affected REST endpoints by modifying the plugin code or using WordPress hooks to restrict access to authenticated and authorized users only.
Employ Web Application Firewalls (WAF) with rules to detect and block unauthorized REST API calls targeting RealPress endpoints.
Monitor website content and email sending logs for unusual activity indicative of exploitation attempts, such as unexpected page creations or email dispatches.
Restrict REST API access to trusted IP addresses or authenticated users where feasible, using server or WordPress configuration.
Educate site administrators about the vulnerability and encourage regular plugin updates and security audits.
Review email sending policies and implement SPF, DKIM, and DMARC records to reduce the impact of potential phishing emails sent from compromised sites.
Conduct penetration testing focused on REST API endpoints to identify any other missing authorization issues.

Description

The RealPress WordPress plugin before 1.1.0 registers the REST routes without proper permission checks, allowing the creation of pages and sending of emails from the site.

Impact

For European organizations, this vulnerability poses a risk primarily to website integrity and email trustworthiness. Unauthorized page creation can lead to website defacement, misinformation, or embedding of malicious content, which can harm brand reputation and user trust. The ability to send emails from the compromised site can facilitate phishing attacks targeting customers or partners, increasing the risk of credential theft or malware infections. Since the vulnerability requires no authentication and can be exploited remotely, it broadens the attack surface significantly. Organizations relying on RealPress for their WordPress sites, especially those with customer-facing portals or transactional email capabilities, face increased risk of operational disruption and reputational damage. The impact on confidentiality and availability is minimal, but the indirect consequences of phishing and brand damage can be substantial. Additionally, regulatory compliance under GDPR may be affected if the unauthorized emails lead to data breaches or privacy violations. The medium severity rating suggests that while the threat is not critical, timely remediation is important to prevent exploitation.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/74f19ff2-d5c0-4bd4-83f2-688ea37022b1/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jan 2026, 20:51 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats