dbcve.org
Social Auto PosterWordPress extension · Accesspressthemes

CVE-2023-26532

HIGH · 8.8 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to after 2.1.4 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 AccessPress Themes Social Auto Poster plugin <= 2.1.4 versions.

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 AccessPress Themes Social Auto Poster WordPress plugin (versions 2.1.4 and below) allows attackers to craft malicious requests that trick authenticated administrators into performing unintended actions, such as posting content to connected social media accounts without their knowledge.

MitigationUpdate to a patched version of the plugin as soon as available; if no patch exists, implement anti-CSRF nonce validation on all state-changing form submissions and admin actions.

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:<= 2.1.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
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 plugin installation
    Check if the AccessPress Themes Social Auto Poster plugin is installed in the WordPress plugins directory or via the WordPress admin Plugins page
    Affected if Plugin is not installed means not affected
  2. Confirm plugin version
    Locate the plugin's main file and read the Version header, or view the version in WordPress admin under Plugins > Installed Plugins
    Affected if Version is 2.1.4 or lower indicates vulnerable range
  3. Check if plugin is active
    In WordPress admin, go to Plugins and verify if Social Auto Poster is currently activated
    Affected if Plugin is active and version is <= 2.1.4 means potentially affected
  4. Inspect for social account connections
    Navigate to the plugin settings page and check if any social media accounts (Facebook, Twitter, LinkedIn, etc.) are connected or configured
    Affected if Social accounts are connected and plugin is vulnerable enables the exploitation vector
  5. Review form actions for nonce validation
    Examine the plugin's source code for form submissions and admin action handlers, looking for wp_verify_nonce or check_admin_referer calls on state-changing requests
    Affected if State-changing forms lack nonce validation means the CSRF vulnerability is present

If the plugin is installed, active, at version 2.1.4 or below, and lacks proper nonce validation on form submissions, the environment is affected by this CSRF vulnerability.

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 2.1.4
Interim mitigation

Update to a patched version of the plugin as soon as available; if no patch exists, implement anti-CSRF nonce validation on all state-changing form submissions and admin actions.

Recommended fix Moderate confidence

Latest available version of Social Auto Poster (newer than 2.1.4)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Update Social Auto Poster plugin to the latest available version from the WordPress plugin repository or AccessPress Themes.
  3. 3. Verify the update completed successfully by checking the installed plugins page.
  4. 4. Test critical functionality of the plugin to ensure it works correctly after the update.
  5. 5. Monitor for any unusual behavior or errors following the update.

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

Fix this in Social Auto Poster Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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