dbcve.org
Post State TagsWordPress extension · Brandbrilliance

CVE-2023-32588

HIGH · 8.8 CVSS v3.1 Published 2023-11-13
Fix available
A fix is available. Upgrade to after 2.0.6 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 BRANDbrilliance Post State Tags plugin <= 2.0.6 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 BRANDbrilliance Post State Tags WordPress plugin allows attackers to induce authenticated administrators to perform unintended state-changing actions via crafted requests.

MitigationUpdate plugin to version >2.0.6 which should include proper nonce/CSRF token validation; alternatively, implement nonces on all state-modifying forms and AJAX actions within the plugin.

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
Post State TagsWordPress extension
Affected:<= 2.0.6

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 and version
    In WordPress admin, go to Plugins > Installed Plugins. Locate 'Brandbrilliance Post State Tags' and check the version number listed under the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag.
    Affected if The plugin is installed and its version is 2.0.6 or lower.
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins. Verify that 'Brandbrilliance Post State Tags' is activated (the plugin must be active for the CSRF vulnerability to be exploitable).
    Affected if The plugin is activated.
  3. Check for state-modifying functionality exposure
    Inspect the plugin's admin interface for any forms, buttons, or AJAX actions that modify post states (such as tagging, categorizing, or changing post status). These are the endpoints that could be targeted by CSRF attacks.
    Affected if The plugin exposes any state-modifying forms or AJAX actions to administrators.
  4. Inspect plugin source for CSRF protection
    If you have file system access, examine the plugin's PHP files for nonce verification functions (wp_verify_nonce, check_admin_referer) on any state-changing operations. Search for action handlers that modify post data.
    Affected if No nonce verification is found on state-modifying actions, or nonces are missing entirely from these functions.

You are affected if the Brandbrilliance Post State Tags plugin is installed with version 2.0.6 or lower and is currently active, exposing state-modifying admin actions without proper CSRF token validation.

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.0.6
Interim mitigation

Update plugin to version >2.0.6 which should include proper nonce/CSRF token validation; alternatively, implement nonces on all state-modifying forms and AJAX actions within the plugin.

Recommended fix Moderate confidence

Latest version available in WordPress Plugin Repository (version > 2.0.6)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Post State Tags plugin in the list
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, you can update manually by downloading the latest version from the WordPress Plugin Repository and uploading it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running on a version higher than 2.0.6

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

Fix this in Post State Tags 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-32588 — 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-32588 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