Social Auto PosterWordPress extension · Wpwebinfotech

CVE-2024-6750

HIGH · 7.5 CVSS v3.1 Published 2024-07-24
Fix available
A fix is available. Upgrade to 5.3.15 or later.
See remediation →
84/100
Remediation priority · High
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 Auto Poster plugin for WordPress is vulnerable to unauthorized access, modification, and loss of data due to a missing capability check on multiple functions in all versions up to, and including, 5.3.14. This makes it possible for unauthenticated attackers to add, modify, or delete post meta and plugin options.

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 Auto Poster WordPress plugin lacks capability checks on multiple functions, allowing unauthenticated attackers to directly modify post meta and plugin options. This is a broken access control vulnerability (CWE-862) where WordPress functions meant to be restricted are exposed without authorization, enabling arbitrary data modification.

MitigationUpdate the plugin to the latest version once available. Until then, restrict access to vulnerable endpoints via server-level configuration or disable the plugin if the risk is unacceptable. Implement proper WordPress capability checks (e.g., current_user_can()) on all affected functions.

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 Auto PosterWordPress extension
Affected:< 5.3.15

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Verify Social Auto Poster plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder containing 'social-auto-poster' or 'wpwebinfotech'. Check if the plugin appears in the list.
    Affected if The plugin is installed and active.
  2. Determine installed plugin version
    In WordPress admin, click on the plugin to view its details and locate the version number. Alternatively, open the main plugin PHP file (usually social-auto-poster.php or similar in the plugin folder) and look for the 'Version' header comment.
    Affected if The version number is less than 5.3.15 (e.g., 5.3.14, 5.3.0, 4.x, etc.).
  3. Inspect plugin options for unauthorized changes
    In WordPress admin, navigate to the plugin settings page (usually under a menu item like Social Auto Poster or WPWeb > Social Auto Poster). Review all saved options for unexpected values, new or modified social media accounts, altered posting schedules, or unfamiliar configuration settings.
    Affected if Plugin options have been modified without administrator action, or unfamiliar settings/accounts are present.
  4. Check for unexpected post meta modifications
    Query the wp_postmeta table in the database, or use a plugin like WP Data Access or WP-CLI to search for post meta entries associated with the Social Auto Poster plugin (typically prefixed with '_sap_' or 'social_auto_poster_') that were created or modified unexpectedly.
    Affected if Post meta entries exist for posts you did not intend to have autoposted, or meta values have been altered without authorization.

Your environment is affected if the Social Auto Poster plugin by Wpwebinfotech is installed with a version lower than 5.3.15, as unauthenticated attackers can modify plugin options and post meta without capability checks.

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 5.3.15 or later
Fixed in 5.3.15
Interim mitigation

Update the plugin to the latest version once available. Until then, restrict access to vulnerable endpoints via server-level configuration or disable the plugin if the risk is unacceptable. Implement proper WordPress capability checks (e.g., current_user_can()) on all affected functions.

Recommended fix High confidence

Social Auto Poster version 5.3.15

  1. Check the currently installed version of Social Auto Poster plugin in WordPress admin under Plugins > Installed Plugins
  2. Backup the WordPress database and files before performing any updates
  3. Update Social Auto Poster plugin to version 5.3.15 or later through WordPress admin: Plugins > Installed Plugins > Update Now next to Social Auto Poster
  4. Alternatively, update via WordPress > Dashboard > Updates or upload the new version manually
  5. Verify the update was successful by confirming the plugin version shows 5.3.15 or higher

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

Fix this in Social Auto Poster Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6750 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