dbcve.org
PremmerceWordPress extension

CVE-2023-23719

HIGH · 8.8 CVSS v3.1 Published 2023-07-17
Fix available
A fix is available. Upgrade to after 1.3.17 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 Premmerce plugin <= 1.3.17 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 Premmerce WordPress plugin affecting versions 1.3.17 and below. This allows attackers to trick authenticated users into performing unintended administrative actions by forging requests.

MitigationUpdate Premmerce plugin to version newer than 1.3.17 when available. If no vendor update exists, implement anti-CSRF nonce validation on all form submissions and AJAX handlers 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
PremmerceWordPress extension
Affected:<= 1.3.17

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 Premmerce plugin installation
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and locate Premmerce in the list
    Affected if Premmerce plugin is not found in the installed plugins list, then this CVE does not apply
  2. Check installed Premmerce version
    In the Plugins list, view the version number displayed under the Premmerce plugin name
    Affected if The version shown is 1.3.17 or any version lower than 1.3.17
  3. Confirm plugin admin functionality is active
    Access the Premmerce plugin settings page in WordPress admin panel to verify the plugin has active administrative functions
    Affected if The plugin has active admin settings or features that perform administrative actions
  4. Inspect form submissions for nonce protection
    Examine the plugin PHP files for form submissions and AJAX handlers. Look for calls to wp_verify_nonce, wp_nonce_field, or check_admin_referer in files within the premmerce directory
    Affected if Form submissions and AJAX handlers lack nonce validation code, meaning CSRF protection is missing

You are affected if the Premmerce plugin is installed with version 1.3.17 or lower and the plugin handles administrative actions without proper nonce validation on forms and AJAX requests.

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.17
Interim mitigation

Update Premmerce plugin to version newer than 1.3.17 when available. If no vendor update exists, implement anti-CSRF nonce validation on all form submissions and AJAX handlers within the plugin.

Fix this in Premmerce 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-23719 — 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-23719 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