CVE-2025-5920VulnerabilityPublished 4 Jul 2025Updated 8 Jul 2025

CVE-2025-5920: Sharable Password Protected Posts (WordPress plugin) · Insertion of Sensitive Information Into Sent Data

Affects Sharable Password Protected Posts (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% 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:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 4 Jul 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.

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 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
Sharable Password Protected Posts	Affected =0	Fixed in–

AI-suggested

European organizations should immediately verify if their WordPress installations use the Sharable Password Protected Posts plugin and identify the version in use. If the plugin version is prior to 1.1.1, they should upgrade to the latest version as soon as it becomes available. In the absence of an official patch, administrators should consider disabling the plugin temporarily to prevent exposure. Additionally, organizations can restrict access to the WordPress REST API endpoints by implementing authentication requirements or IP whitelisting to prevent unauthorized retrieval of sensitive GET parameters. Web Application Firewalls (WAFs) can be configured to detect and block suspicious requests targeting the REST API that include the secret key parameter. Reviewing and minimizing the use of password-protected posts for highly sensitive data until the vulnerability is resolved is advisable. Monitoring logs for unusual access patterns to REST API endpoints can help detect exploitation attempts. Finally, organizations should educate content creators about the risks of sharing sensitive information via this plugin and encourage alternative secure sharing methods.

Description

The Sharable Password Protected Posts before version 1.1.1 allows access to password protected posts by providing a secret key in a GET parameter. However, the key is exposed by the REST API.

Impact

For European organizations, especially those relying on WordPress sites with sensitive or confidential content shared via the Sharable Password Protected Posts plugin, this vulnerability poses a substantial risk to data confidentiality. Unauthorized disclosure of protected posts could lead to exposure of intellectual property, internal communications, or personal data, potentially violating GDPR and other privacy regulations. The breach of confidentiality could damage organizational reputation, lead to regulatory fines, and erode customer trust. Since the vulnerability requires no authentication or user interaction and can be exploited remotely over the network, attackers can easily automate data harvesting. This is particularly concerning for sectors such as finance, healthcare, legal, and government entities in Europe that often use password-protected posts to share sensitive information internally or with clients. The lack of impact on integrity and availability limits the threat to data leakage rather than system disruption, but the confidentiality breach alone is critical under European data protection frameworks.

CWE-201Insertion of Sensitive Information Into Sent Data (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Requirements
Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
Implementation
Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere.
System Configuration
Setup default error messages so that unexpected errors do not disclose sensitive information.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Exploiting Incorrectly Configured SSL/TLS (opens in a new tab)
WiFi MAC Address Tracking (opens in a new tab)
WiFi SSID Tracking (opens in a new tab)
Cellular Broadcast Message Request (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/dddd6074-1e1f-441f-86f7-316c30262c70/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2025, 21:18 UTC

WeaknessesCWE-201

Technical details

References

Community reviews

Related threats