Feed Them SocialWordPress extension · Slickremix
CVE-2015-9350
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 feed-them-social plugin before 1.7.0 for WordPress has reflected XSS in the Facebook Feeds load more button.
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 confidenceThe feed-them-social WordPress plugin before version 1.7.0 contains a reflected cross-site scripting (XSS) vulnerability in the Facebook Feeds 'load more' button functionality. The vulnerability allows attackers to inject malicious scripts through unsanitized input that gets reflected back to users when they interact with the load more button.
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
Feed Them SocialWordPress extension
< 1.7.0CVSS 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 the Feed Them Social plugin is installedIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'Feed Them Social' or 'Slickremix Feed Them Social' in the list of active plugins.Affected if The plugin appears in the list of installed plugins.
-
Determine the installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins, find Feed Them Social, and view the version number displayed below the plugin name. Alternatively, check the plugin files in /wp-content/plugins/feed-them-social/ for a version indicator in the main plugin file header.Affected if The version shown is below 1.7.0 (for example, 1.6.9, 1.5.0, etc.).
-
Identify if Facebook Feeds are in useReview any pages or posts where the Facebook Feeds shortcode or widget is embedded. Check for the presence of Facebook feed shortcodes such as [feed_them_facebook] or Facebook feed widgets in your widget areas.Affected if Facebook feeds are currently displayed on the site using this plugin.
-
Confirm the load more feature is accessibleVisit a page displaying a Facebook feed and locate the 'Load More' button or pagination controls within the feed display. The vulnerability exists in this load more button functionality.Affected if A Facebook feed with a functional load more button is present and accessible to site visitors.
The site is affected if Feed Them Social plugin version is below 1.7.0 AND Facebook Feeds with the load more functionality are in use on the 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 data1.7.0
Update the feed-them-social plugin to version 1.7.0 or later, which includes proper input sanitization. Alternatively, remove the plugin if it is not required.
Fix this in Feed Them Social
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9350 — 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-9350 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