Wp RollbackWordPress extension · Impress
CVE-2015-9343
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe wp-rollback plugin before 1.2.3 for WordPress has CSRF.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe wp-rollback WordPress plugin before version 1.2.3 contains a Cross-Site Request Forgery (CSRF) vulnerability. This allows attackers to trick authenticated administrators into performing unintended actions by crafting malicious requests, likely related to the plugin's rollback functionality for WordPress themes and plugins.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp RollbackWordPress extension
< 1.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if wp-rollback plugin is installedNavigate to WordPress Admin > Plugins and look for 'Wp Rollback' or 'Impress Wp Rollback' in the installed plugins listAffected if Plugin is not listed in the WordPress admin panel, meaning it is not installed and therefore not affected
-
Identify the installed version numberIn WordPress Admin > Plugins, find the wp-rollback plugin entry and look for the version number displayed below the plugin name, or check the main plugin file (wp-rollback.php) for the 'Version' header commentAffected if Unable to locate version information or the plugin file is missing
-
Compare version against affected rangeReview the version number found (for example 1.2.0, 1.2.2, or 1.2.3) and compare it to the vulnerable range: any version before 1.2.3 (such as 1.2.0, 1.2.1, 1.2.2) is affectedAffected if Installed version is less than 1.2.3 (for example 1.2.0, 1.2.1, or 1.2.2)
-
Confirm admin access is requiredUnderstand that this CSRF vulnerability requires the victim to be an authenticated administrator with access to the WordPress admin dashboard where the wp-rollback plugin is activeAffected if The site has administrators using the wp-rollback plugin functionality in the WordPress admin area
A user is affected if the wp-rollback plugin is installed with a version lower than 1.2.3 and an authenticated administrator accesses the plugin's rollback features.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.2.3
Update wp-rollback plugin to version 1.2.3 or later. If unable to update immediately, disable the plugin until the patch can be applied. The fix involves implementing anti-CSRF tokens (nonces) in all state-changing operations.
Fix this in Wp Rollback
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-9343 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data