Wp DocsWordPress extension · Androidbubble
CVE-2024-35696
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Fahad Mahmood WP Docs allows Reflected XSS.This issue affects WP Docs: from n/a through 2.1.3.
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 confidenceReflected XSS vulnerability in WP Docs WordPress plugin allows injection of malicious JavaScript through unsanitized user input that gets reflected in generated web pages, potentially enabling session hijacking or phishing attacks.
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 DocsWordPress extension
< 2.1.4CVSS 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.
-
Verify WP Docs plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Locate 'WP Docs' or 'Androidbubble Wp Docs' in the list.Affected if WP Docs plugin appears in the installed plugins list and is activated
-
Check installed WP Docs versionIn the Plugins list, look for the version number displayed under the WP Docs plugin name. Alternatively, open wp-content/plugins/wp-docs/readme.txt and check the version in the header, or query the wp_options table for the option_name containing 'wp_docs' version.Affected if The installed version is any version prior to 2.1.4 (e.g., 2.1.3, 2.1.2, etc.)
-
Confirm plugin frontend functionality is accessibleVisit the WordPress site and attempt to access any WP Docs public-facing pages or shortcodes (commonly /docs/ or similar URL paths). Check if the plugin renders user input fields or displays query string parameters in the page output.Affected if WP Docs public pages load and accept user input through URL parameters (e.g., ?doc=, ?id=, or custom parameters) that get reflected in the HTML output
-
Inspect for unsanitized parameter reflectionAppend a test parameter to a WP Docs URL, such as ?test= <script>alert(1)</script> or ?doc=<script>alert(1)</script>, and view the page source. Search for the raw parameter value appearing without escaping functions like esc_html(), esc_attr(), or similar.Affected if The test parameter value appears unescaped in the rendered HTML source, indicating the vulnerability is present and exploitable
The environment is affected if WP Docs plugin versions below 2.1.4 are installed and active, and the plugin's frontend functionality that reflects $_GET parameters is accessible without proper output encoding.
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.
dbcve · scoped2.1.4
Update WP Docs to the patched version when available. Until then, implement output encoding and input validation using WordPress security functions ($_GET parameter sanitization, esc_html(), esc_attr() etc.) at all user input reflection points.
2.1.4
- 1. Create a full backup of your WordPress site (database and files) before making any changes.
- 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
- 3. Locate the WP Docs plugin in the list.
- 4. If an update is available, click 'Update Now' to upgrade to version 2.1.4 or later.
- 5. Alternatively, navigate to Dashboard > Updates to check for and apply the plugin update.
- 6. After updating, verify the plugin version shows 2.1.4 or higher under Plugins > Installed Plugins.
- 7. Test the plugin functionality to ensure it works correctly after the update.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Docs
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35696 — 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-2024-35696 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