Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running WP Rollback ≤3.1.2
-
ExploitSend crafted request to plugin endpoint
-
ExecutionTrigger sensitive data into response
-
ImpactRetrieve embedded sensitive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Outbound data filtering
|
| Exploitation Conditions | Exploitation targets the WP Rollback plugin (versions from unknown through 3.1.2) on WordPress; the CVSS vector indicates no authentication (PR:N) and no user interaction (UI:N) are required, but the high attack complexity (AC:H) means success depends on conditions the attacker does not control - such as sensitive data actually being present/embedded, specific plugin state, or timing. The description does not name a specific configuration toggle; the limiting factors are therefore the high complexity and the requirement that exploitable sensitive data exist in the relevant responses. The precise data exposed is not described and should be confirmed with the vendor/Patchstack advisory to assess real impact. |
| Impact | This is a moderate-severity information disclosure flaw (CWE-201) in the WP Rollback WordPress plugin, rated CVSS 5.9. The provided CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates a network-reachable, unauthenticated vector with high attack complexity, high confidentiality impact, and no integrity or availability impact - consistent with an attacker retrieving embedded sensitive data rather than achieving code execution. The signals are internally consistent but modest: the single-source Patchstack reference drives the entry, and there is NO EPSS score, NO CISA KEV listing, and NO public proof-of-concept provided in the input, so exploitation probability cannot be quantified from the data. The AC:H rating is the key moderating factor - it implies exploitation depends on conditions outside the attacker's control (timing, specific configuration, or data actually being present/embedded), which lowers real-world urgency below what the C:H component alone might suggest. Net: this is a credible but not high-priority issue absent evidence of active exploitation; the high confidentiality impact warrants patching, but the high complexity and lack of any exploitation signal argue against emergency treatment. Note the description's vague phrasing ('Retrieve Embedded Sensitive Data') does not specify WHAT data is exposed, so the C:H rating should be verified against the actual exposed data before assuming severe impact. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker interacts with a WP Rollback-equipped WordPress site and, under specific conditions reflected by the high attack complexity, causes sensitive information to be embedded in server responses they can observe. The exposed data is then harvested for reconnaissance or further attacks. No public exploit code is identified in the provided data, and the AC:H rating suggests the attack is not trivially repeatable on demand. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Unauthenticated remote attackers can retrieve embedded sensitive information from WordPress sites running the WP Rollback plugin through version 3.1.2, because the plugin places sensitive data into data it sends back to the client (CWE-201). The flaw is rated CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), meaning no credentials or user interaction are needed but attack complexity is high, so success depends on conditions the attacker does not control - such as the specific sensitive data being present in the affected responses or a particular plugin state. There is no public exploit code identified at time of analysis and no confirmation of active exploitation (CISA KEV); the exposure is limited to confidentiality, with no integrity or availability impact, and the exact data exposed is not described in the available advisory and should be confirmed with the vendor/Patchstack.
RemediationAI
No vendor-released patch version is specified in the available data, so the first step is to check the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wp-rollback/vulnerability/wordpress-wp-rollback-plugin-3-1-2-sensitive-data-exposure-vulnerability?_s_id=cve (and the WP Rollback plugin page/changelog) for the fixed release and upgrade to it as soon as it is published; because exploitation requires no authentication or user interaction, treat this as a priority update for any site where the plugin is active. If no fix is yet available, or if the plugin is not essential, deactivate and remove WP Rollback - the trade-off is loss of its plugin/theme rollback capability, which can be mitigated by taking manual filesystem or database backups before updates instead. Where removal is not acceptable, restrict reachability of the plugin's AJAX/REST and admin-facing endpoints at the perimeter (WAF rules or web server rules blocking unauthenticated requests to WP Rollback paths), noting this is a partial control that can be bypassed and may break legitimate plugin functionality for logged-in admins. Additionally, review any data the plugin returns for embedded secrets - API keys, license tokens, internal paths or configuration values - and rotate anything that may have been exposed, then monitor web logs for anomalous unauthenticated requests to WP Rollback endpoints as a detection measure, with the caveat that logging alone does not prevent disclosure.
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 issue is a CWE-201 (Insertion of Sensitive Information Into Sent Data) weakness in the WordPress plugin WP Rollback, a utility that lets administrators roll back installed plugins and themes to earlier versions. CWE-201 is an outbound/information-flow problem: rather than an attacker injecting input, the application itself includes sensitive values - such as tokens, keys, credentials, internal paths, or configuration data - inside the responses it returns to clients, where a remote party can read them. The affected code base is PHP running inside WordPress, and the CVSS vector AV:N/PR:N/UI:N confirms the vulnerable path is network-reachable without authentication or victim interaction, while AC:H signals that reliable exploitation hinges on preconditions outside the attacker's control (for example, the sensitive data actually being embedded in the response, or a specific plugin/state configuration). The reference to Patchstack's WordPress plugin vulnerability database is consistent with a plugin-specific advisory rather than a core WordPress issue, so the blast radius tracks installations of WP Rollback rather than the CMS itself. No CPE strings were supplied, and the affected range is defined only as versions up to and including 3.1.2.
Know when Wordpress Plugin 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:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-reachable and unauthenticated (AV:N/PR:N) per source; AC:H because disclosure depends on uncontrolled conditions; confidentiality-only impact (C:H, I:N, A:N) matching CWE-201.
Primary rating from Vendor (patchstack).
CVSS VectorVendor: patchstack
DescriptionCVE.org
Insertion of Sensitive Information Into Sent Data vulnerability in Devin Walker WP Rollback wp-rollback allows Retrieve Embedded Sensitive Data.This issue affects WP Rollback: from n/a through 3.1.2.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-96326
GHSA-wwcc-9gfr-hgp3
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB