dbcve.org
Social RocketWordPress extension · Wpsocialrocket

CVE-2024-9697

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to after 1.3.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Social Rocket – Social Sharing Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the tweet_settings_save() and tweet_settings_update() functions in all versions up to, and including, 1.3.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update the plugin's settings.

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 confidence

The Social Rocket WordPress plugin lacks capability checks on the tweet_settings_save() and tweet_settings_update() functions, allowing any authenticated user with Subscriber-level access or higher to modify plugin settings. This is a Broken Access Control vulnerability (CWE-862) where the plugin fails to verify user permissions before allowing configuration changes.

MitigationUpdate to version 1.3.5 or later which should include proper capability checks. If no update is available, manually add current_user_can() checks to both affected functions or restrict access via WAF rules.

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
Social RocketWordPress extension
Affected:<= 1.3.4

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

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

  1. Check if Social Rocket plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Social Rocket' by WPSocialRocket, or check the /wp-content/plugins/ directory for a social-rocket folder.
    Affected if The plugin is not installed or has been removed.
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Social Rocket, or open the main plugin file (social-rocket/social-rocket.php) and look for the 'Version' header in the plugin comment block.
    Affected if Version is 1.3.4 or lower.
  3. Inspect tweet_settings_save() function for capability checks
    Locate the file containing tweet_settings_save() function (typically in includes/admin/ or similar). Open the PHP file and examine the function definition. Look for current_user_can() or similar permission checks at the function start.
    Affected if No capability check (like current_user_can('manage_options')) is present at the beginning of the function.
  4. Inspect tweet_settings_update() function for capability checks
    Locate the file containing tweet_settings_update() function. Open the PHP file and examine the function definition. Verify if a current_user_can() check exists before any settings modification logic.
    Affected if No capability check is found at the start of tweet_settings_update().
  5. Verify any authenticated user can access settings
    Create a test subscriber-level user account if not existing. Log in with that account and attempt to access the Social Rocket settings page (usually under Settings > Social Rocket or a dedicated Twitter/settings tab).
    Affected if A subscriber-level user can access or submit the plugin settings form without being redirected or denied.

Your environment is affected if Social Rocket plugin version is 1.3.4 or lower AND the tweet_settings_save() and tweet_settings_update() functions lack capability checks, allowing any authenticated user to modify settings.

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 a release after 1.3.4
Interim mitigation

Update to version 1.3.5 or later which should include proper capability checks. If no update is available, manually add current_user_can() checks to both affected functions or restrict access via WAF rules.

Recommended fix High confidence

Social Rocket version 1.3.5 or later

  1. 1. Log in to the WordPress admin dashboard.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the Social Rocket plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to the latest version.
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload version 1.3.5 or later if automatic update is not available.
  6. 6. After updating, verify the plugin is functioning correctly and review the settings to ensure they are configured as intended.

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

Fix this in Social Rocket Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9697 — 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-2024-9697 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