FeedwordpressWordPress extension · Feedwordpress Project
CVE-2015-9358
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 feedwordpress plugin before 2015.0514 for WordPress has XSS via add_query_arg() and remove_query_arg().
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 FeedWordPress plugin before version 2015.0514 for WordPress contains a cross-site scripting (XSS) vulnerability caused by improper use of WordPress add_query_arg() and remove_query_arg() functions. These URL manipulation functions were not properly escaped before being output in the plugin's admin interface, allowing injection of malicious script content.
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
FeedwordpressWordPress extension
< 2015.0514CVSS 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.
-
Verify FeedWordPress plugin is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins, or check for the existence of /wp-content/plugins/feedwordpress/ directory on the serverAffected if FeedWordPress plugin is present in the WordPress installation
-
Check installed FeedWordPress versionIn WordPress admin, go to Plugins > Installed Plugins and find FeedWordPress to view its version number; alternatively, open the main plugin file (feedwordpress.php) and look for the Version header in the plugin comment blockAffected if Installed version is lower than 2015.0514 (e.g., 2015.0315, 2014.x.x, etc.)
-
Inspect plugin files for vulnerable URL function usageExamine the main plugin file (feedwordpress.php) and admin interface files (such as admin-ui.php) for uses of add_query_arg() or remove_query_arg() that are output directly without esc_url() or esc_attr() escaping functionsAffected if Code contains add_query_arg() or remove_query_arg() output statements without proper escaping functions like esc_url() or esc_attr()
-
Confirm access to WordPress admin interfaceVerify you have administrator-level access to the WordPress site, as the XSS vulnerability is present in the plugin's admin interface pagesAffected if User has admin access to the WordPress site with FeedWordPress installed
Your environment is affected if FeedWordPress plugin version is below 2015.0514 and the plugin is installed on your WordPress site.
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 data2015.0514
Update the FeedWordPress plugin to version 2015.0514 or later to remediate this XSS vulnerability. Alternatively, manually escape add_query_arg() and remove_query_arg() outputs using esc_url() or esc_attr() in the affected plugin files.
Fix this in Feedwordpress
Scoped from the published advisory
- 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-2015-9358 — 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-2015-9358 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