All In One Wp Security \& FirewallWordPress extension · Tipsandtricks Hq
CVE-2016-10867
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 all-in-one-wp-security-and-firewall plugin before 4.0.6 for WordPress has XSS in settings pages.
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 all-in-one-wp-security-and-firewall WordPress plugin before version 4.0.6 contains a Cross-Site Scripting (XSS) vulnerability in its settings pages. This allows attackers to inject malicious scripts through unsanitized user input in plugin settings, which then executes in the browsers of authenticated users viewing those pages.
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
All In One Wp Security \& FirewallWordPress extension
< 4.0.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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 plugin installation directoryCheck your WordPress wp-content/plugins directory for a folder named 'all-in-one-wp-security-and-firewall' or similar variant containing 'all-in-one-wp-security'Affected if The plugin folder exists in the WordPress installation
-
Identify the installed plugin versionOpen the main plugin file (usually index.php or the primary plugin PHP file) and locate the version comment/header, or check the WordPress admin plugins page for the installed version numberAffected if The displayed version number is below 4.0.6 (for example: 4.0.5, 4.0.4, etc.)
-
Verify plugin status is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm the All In One WP Security plugin shows as 'Active'Affected if The plugin is active and running on the site
-
Confirm settings page access existsLog into WordPress admin and navigate to WP Security > Settings to confirm the plugin settings pages are accessibleAffected if You can access the plugin settings pages as an authenticated administrator user
The environment is affected if the installed version of the all-in-one-wp-security-and-firewall plugin is any version prior to 4.0.6.
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 data4.0.6
Upgrade the all-in-one-wp-security-and-firewall plugin to version 4.0.6 or later. If immediate upgrade is not possible, restrict administrative access and audit existing admin sessions for suspicious activity.
Fix this in All In One Wp Security \& Firewall
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10867 — 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-10867 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