dbcve.org
Social Auto PosterWordPress extension · Wpwebinfotech

CVE-2024-49272

HIGH · 8.8 CVSS v3.1 Published 2024-10-20
Fix available
A fix is available. Upgrade to 5.3.16 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in wpweb Social Auto Poster social-auto-poster allows Cross Site Request Forgery.This issue affects Social Auto Poster: from n/a through <= 5.3.15.

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

Cross-Site Request Forgery (CSRF) vulnerability in the wpweb Social Auto Poster WordPress plugin allows attackers to induce authenticated administrators to perform unintended state-changing actions (e.g., modifying posting settings, connecting/disconnecting social accounts). The lack of anti-CSRF tokens on sensitive operations enables malicious requests to be forged.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions that modify plugin settings or user data, and validate nonce verification server-side on receipt. Additionally, verify Origin/Referer headers and set SameSite attribute on session cookies.

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.16

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Social Auto Poster plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Social Auto Poster' by Wpwebinfotech. Note the installed version displayed.
    Affected if The plugin is installed and the version shown is below 5.3.16 (e.g., 5.3.15, 5.3.14, etc.)
  2. Check plugin version via file system
    If you have file system access, navigate to /wp-content/plugins/social-auto-poster/includes/ or similar and locate the main plugin file (often readme.txt or main .php file) to read the Version header.
    Affected if The version extracted from plugin files is less than 5.3.16
  3. Inspect admin settings forms for nonce fields
    Access the plugin settings pages (typically under Social Auto Poster menu in WP admin). View page source (right-click > View Page Source) and search for forms that handle sensitive actions (posting settings, social account connections). Look for input fields containing '_wpnonce' or 'nonce' within these forms.
    Affected if Forms that modify posting settings or social account connections do not contain any _wpnonce or nonce input fields
  4. Inspect AJAX action handlers for nonce verification
    If you can access plugin PHP files via file system or a file manager, search for AJAX hooks (add_action('wp_ajax_...')) and check if they call wp_verify_nonce() or check_admin_referer() before processing requests.
    Affected if AJAX handlers that modify settings or social connections lack nonce verification calls
  5. Verify cookie SameSite attribute
    Using browser developer tools (Application > Cookies), inspect cookies set by your WordPress site. Check if the WordPress session cookie has the SameSite attribute set, or inspect the Set-Cookie headers via Network tab when logging in.
    Affected if Session cookies lack SameSite=Strict or SameSite=Lax attribute

You are affected if the Social Auto Poster plugin is installed with a version lower than 5.3.16 AND sensitive plugin actions (settings changes, social account modifications) lack WordPress nonce verification in their forms or AJAX handlers.

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.16 or later
Fixed in 5.3.16
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions that modify plugin settings or user data, and validate nonce verification server-side on receipt. Additionally, verify Origin/Referer headers and set SameSite attribute on session cookies.

Recommended fix High confidence

Social Auto Poster version 5.3.16

  1. 1. Backup your WordPress site and database before updating any plugins.
  2. 2. Navigate to your WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the Social Auto Poster plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to version 5.3.16.
  5. 5. Alternatively, go to Plugins > Add New > Upload and upload version 5.3.16 of the plugin.
  6. 6. After updating, verify the plugin version shows 5.3.16 to confirm the fix is applied.

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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