Wp Maintenance Mode PluginPlugin / extension · WordPress
CVE-2013-3250
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 · uneditedCross-site request forgery (CSRF) vulnerability in the WP Maintenance Mode plugin before 1.8.8 for WordPress allows remote attackers to hijack the authentication of arbitrary users for requests that modify this plugin's settings.
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 · high confidenceCross-site request forgery (CSRF) vulnerability in the WP Maintenance Mode plugin for WordPress versions before 1.8.8 allows remote attackers to modify plugin settings by tricking authenticated administrators into submitting malicious requests, hijacking their session authentication.
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 Maintenance Mode PluginPlugin / extension
<= 1.8.7= 1.8.0= 1.8.1= 1.8.2= 1.8.3= 1.8.4= 1.8.5= 1.8.6CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Locate the WP Maintenance Mode plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'WP Maintenance Mode' in the list. The version number is displayed below the plugin name.Affected if The displayed version is 1.8.7 or lower, or shows any of these exact versions: 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, or 1.8.7.
-
Confirm plugin is activeIn the same Plugins screen, verify the WP Maintenance Mode plugin has the 'Activate' link (meaning it is currently running).Affected if The plugin is activated. An active plugin with a vulnerable version can have its settings modified via CSRF.
-
Check plugin settings accessNavigate to Settings > WP Maintenance Mode in the WordPress admin sidebar. If you can access the plugin settings panel, the CSRF vulnerability can be triggered.Affected if You can access the settings panel with administrator privileges. The CSRF vulnerability allows an attacker to modify these settings by tricking an authenticated admin into visiting a malicious page.
Your environment is affected if the WP Maintenance Mode plugin version is 1.8.7 or lower and the plugin is active, because the missing anti-CSRF tokens in plugin settings forms allow attackers to hijack authenticated admin sessions.
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 dataUpgrade the WP Maintenance Mode plugin to version 1.8.8 or later which includes proper anti-CSRF token validation. Alternatively, implement WordPress nonces on all plugin settings forms and AJAX actions to validate request origin.
Fix this in Wp Maintenance Mode Plugin
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3250 — 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-2013-3250 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