dbcve.org
Feed Them SocialWordPress extension · Slickremix

CVE-2015-9351

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-27
Fix available
A fix is available. Upgrade to 1.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The feed-them-social plugin before 1.7.0 for WordPress has possible shortcode execution 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 confidence

The feed-them-social WordPress plugin before version 1.7.0 contains a vulnerability allowing possible shortcode execution in the Facebook Feeds load more button functionality. This likely allows attackers to inject and execute arbitrary shortcodes or JavaScript via unsanitized input, leading to stored XSS or potentially remote code execution depending on what other shortcodes are registered on the site.

MitigationUpdate the feed-them-social plugin to version 1.7.0 or later to obtain the security fix. If immediate update is not possible, consider disabling the Facebook Feeds functionality or the entire plugin until the patch can be applied.

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
Affected:< 1.7.0

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed version of Feed Them Social plugin
    In WordPress admin, go to Plugins > Installed Plugins > look for 'Feed Them Social' or 'Slickremix Feed Them Social' and note the version number displayed. Alternatively, inspect the main plugin file (feed-them-social.php) and look for the 'Version:' header comment.
    Affected if The displayed version is lower than 1.7.0 (e.g., 1.6.9, 1.6.8, etc.)
  2. Identify if Facebook Feeds shortcode is in use
    Search WordPress posts, pages, and widgets for the Facebook feed shortcode, which typically appears as [feed_them_facebook] or similar variations. Check page editor content and widget areas where shortcodes may be embedded.
    Affected if The shortcode [feed_them_facebook] or its variants are present in any published content on the site.
  3. Check if load more button is enabled for Facebook feeds
    Edit a page or post containing the Facebook feed shortcode and inspect the feed settings. Look for options labeled 'Load More', 'Load More Button', or pagination settings within the feed configuration.
    Affected if The Facebook feed is configured with a load more button or pagination feature enabled.
  4. Verify shortcode processing accepts unsanitized input
    Inspect the plugin files related to Facebook feeds, specifically files handling the load-more AJAX callback. Look for direct use of $_POST or $_GET parameters in shortcode attributes without sanitization functions like esc_attr() or sanitize_text_field().
    Affected if The plugin code passes user input directly to shortcode output without proper sanitization, or the load-more functionality processes raw input from request parameters.

You are affected if the Feed Them Social plugin version is below 1.7.0 AND the Facebook Feeds with load-more button functionality is actively used on your site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.7.0 or later
Fixed in 1.7.0
Interim mitigation

Update the feed-them-social plugin to version 1.7.0 or later to obtain the security fix. If immediate update is not possible, consider disabling the Facebook Feeds functionality or the entire plugin until the patch can be applied.

Recommended fix High confidence

1.7.0

  1. Backup the WordPress site and database before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'Feed Them Social' in the plugin list
  4. Click 'Update now' if an update to version 1.7.0 or later is available, or manually upload version 1.7.0+ of the plugin
  5. Verify the plugin version is 1.7.0 or higher after updating
  6. Test the Facebook Feeds 'Load More' button functionality to confirm the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Feed Them Social Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-9351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-9351 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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