CVE-2024-9607
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 10Web Social Post Feed plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 1.2.9. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Please note this is only exploitable when the leave a review notice is present.
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 10Web Social Post Feed WordPress plugin (versions up to 1.2.9) contains a reflected cross-site scripting (XSS) vulnerability. The flaw stems from the use of WordPress add_query_arg() function to modify URLs without proper output escaping/sanitization. This allows injection of arbitrary JavaScript through specially crafted URL parameters. Exploitation requires the 'leave a review' admin notice to be present and tricking a user into clicking a malicious link.
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<= 1.2.9CVSS 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 plugin installation and versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate '10Web Social Post Feed' and note the version number displayed.Affected if The installed version is 1.2.9 or lower.
-
Confirm vulnerable version rangeCompare the installed version against the affected range: versions up to and including 1.2.9 are vulnerable.Affected if The installed version is 1.2.9 or any earlier version.
-
Locate the vulnerable code patternInspect the plugin files for usage of add_query_arg() without corresponding esc_url() or esc_attr() when building URLs. The vulnerability lies in how URLs are constructed for admin notices.Affected if The plugin code uses add_query_arg() to modify URLs and those URLs are not properly escaped before output.
-
Check for admin notice functionalitySearch the plugin source code for 'leave a review' notice implementation or admin notice hooks that render the vulnerable URL. This is the exploitation vector.Affected if The plugin contains admin notice code that displays the 'leave a review' prompt and constructs URLs using add_query_arg().
If the 10Web Social Post Feed plugin is installed at version 1.2.9 or lower, the environment is affected by this reflected XSS vulnerability.
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 · scopedUpdate the 10Web Social Post Feed plugin to version 1.2.10 or later. Until patched, warn administrators against clicking untrusted links while logged into WordPress admin areas where this notice appears.
1.3.0 or later
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the '10Web Social Post Feed' plugin
- Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/10web-social-post-feed and upload it
- After updating, verify the plugin version is 1.3.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9607 — 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-9607 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