All In One Wp Security \& FirewallWordPress extension · Tipsandtricks Hq
CVE-2016-10868
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.5 for WordPress has XSS in the blacklist, file system, and file change detection 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 confidenceCross-site scripting (XSS) vulnerability in the all-in-one-wp-security-and-firewall WordPress plugin versions prior to 4.0.5. The flaw exists in blacklist, file system, and file change detection settings pages, allowing injection of malicious scripts.
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.5CVSS 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.0/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 directoryAccess your WordPress site via FTP or file manager and navigate to /wp-content/plugins/all-in-one-wp-security-and-firewall/Affected if The plugin directory exists on the server
-
Identify the installed plugin versionOpen the main plugin file (usually all-in-one-wp-security-and-firewall.php) and locate the version comment or version variable at the top of the fileAffected if The version number found is less than 4.0.5 (for example, 4.0.4, 4.0.3, etc.)
-
Verify plugin is activeLog into WordPress admin panel and navigate to Plugins > Installed Plugins, or check the active_plugins option in the wp_options database tableAffected if The plugin is installed and active in WordPress
-
Check access to vulnerable settings pagesLog into WordPress admin and navigate to WP Security > Blacklist, WP Security > Filesystem, and WP Security > File Change Detection pages to confirm they are accessibleAffected if You have access to any of these three settings pages (blacklist, filesystem, or file change detection) and the plugin version is below 4.0.5
You are affected if the all-in-one-wp-security-and-firewall plugin is installed with a version lower than 4.0.5 and you have access to the blacklist, filesystem, or file change detection settings pages.
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.5
Update the all-in-one-wp-security-and-firewall plugin to version 4.0.5 or later to remediate this XSS vulnerability.
Fix this in All In One Wp Security \& Firewall
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-10868 — 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-10868 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