Simple Add Pages Or PostsWordPress extension · Mijnpress
CVE-2016-10883
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 simple-add-pages-or-posts plugin before 1.7 for WordPress has CSRF for deleting users.
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 confidenceThe simple-add-pages-or-posts WordPress plugin before version 1.7 lacks proper CSRF (Cross-Site Request Forgery) protection on its user deletion functionality. An attacker can craft a malicious page that, when visited by an authenticated administrator, will silently trigger user deletion requests without the victim's consent, exploiting the trusted session.
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
Simple Add Pages Or PostsWordPress extension
< 1.7CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 simple-add-pages-or-posts plugin installationCheck your WordPress plugins directory for a folder named 'simple-add-pages-or-posts' or 'mijnpress-simple-add-pages-or-posts'. In a standard WordPress setup, this would be under wp-content/plugins/.Affected if The plugin folder exists in your plugins directory.
-
Determine the installed plugin versionOpen the main plugin file (usually simple-add-pages-or-posts.php) and look for the version string in the plugin header comment, or check the readme.txt file for the 'Stable tag' entry.Affected if The version listed is lower than 1.7, or no version is declared (indicating an old installation).
-
Verify the plugin is activeLog in to WordPress admin and navigate to Plugins > Installed Plugins. Check if 'Simple Add Pages Or Posts' or 'Mijnpress Simple Add Pages Or Posts' is listed as active.Affected if The plugin is active and the version is below 1.7.
-
Check for user deletion functionalityAccess the plugin settings page in WordPress admin (usually under Settings or the plugin's own menu). Look for any user management, user deletion, or user removal features.Affected if The plugin exposes a user deletion feature and runs on a version below 1.7.
You are affected if the simple-add-pages-or-posts plugin is installed, active, and running at a version lower than 1.7, as this version range lacks CSRF protection on user deletion operations.
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.7
Update the simple-add-pages-or-posts plugin to version 1.7 or later, which includes anti-CSRF token validation for sensitive operations like user deletion.
Fix this in Simple Add Pages Or Posts
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10883 — 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-2016-10883 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