dbcve.org
Publish Confirm MessageWordPress extension · Arulprasadj

CVE-2023-32124

HIGH · 8.8 CVSS v3.1 Published 2023-10-12
Fix available
A fix is available. Upgrade to after 1.3.1 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 Arul Prasad J Publish Confirm Message plugin <= 1.3.1 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 Arul Prasad J Publish Confirm Message WordPress plugin versions 1.3.1 and below allows attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or publishing content via crafted malicious requests.

MitigationUpdate the plugin to the latest version (>1.3.1) once available; alternatively, disable the plugin until a patched version is released.

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
Publish Confirm MessageWordPress extension
Affected:<= 1.3.1

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. Identify if the plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'arulprasadj-publish-confirm-message' or 'arul-prasad-j-publish-confirm-message', or view installed plugins in the WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder exists in the plugins directory or appears in the WordPress admin plugin list
  2. Determine the installed version
    Open the main plugin PHP file (usually named similarly to the folder) and look for the version comment/header, or check the version column in Plugins > Installed Plugins in WordPress admin
    Affected if The reported version is 1.3.1 or lower (e.g., 1.3.1, 1.3.0, 1.2.0, etc.)
  3. Verify if the plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to see if the plugin is currently activated, or query the wp_options table for the active_plugins option
    Affected if The plugin shows as 'Active' in the WordPress admin or appears in the active_plugins option in the database
  4. Confirm the plugin handles admin actions securely
    Review the plugin PHP code for nonce verification on admin action functions (look for wp_verify_nonce, check_admin_referer, or nonce_field) in files handling settings changes or publish actions
    Affected if Admin actions such as saving settings or publishing content can be triggered without a valid nonce token (missing or improperly validated CSRF protection)

Your environment is affected if the Arulprasadj Publish Confirm Message plugin is installed, active, and running version 1.3.1 or lower.

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

Update the plugin to the latest version (>1.3.1) once available; alternatively, disable the plugin until a patched version is released.

Recommended fix Moderate confidence

Latest version > 1.3.1

  1. Log in to the WordPress admin dashboard.
  2. Navigate to Plugins > Installed Plugins.
  3. Locate the 'Publish Confirm Message' plugin.
  4. Click 'Update Now' to upgrade to the latest version available (ensure the new version is greater than 1.3.1).

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

Fix this in Publish Confirm Message Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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