dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-32293

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in Realwebcare WRC Pricing Tables allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WRC Pricing Tables: from n/a through 2.3.7.

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

The WRC Pricing Tables WordPress plugin through version 2.3.7 contains a missing authorization vulnerability that allows unauthenticated users to access functionality intended only for privileged users due to incorrectly configured access control security levels.

MitigationImplement proper capability checks and authorization verification for all sensitive operations in the plugin; ensure all admin actions require valid nonce tokens and appropriate user capabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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. Confirm WRC Pricing Tables plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WRC Pricing Tables' or 'WRC Pricing Tables (aka WRC)' in the list.
    Affected if The plugin appears in the installed plugins list, regardless of whether it is activated or not.
  2. Identify the installed plugin version
    In the Plugins list, look for the version number displayed beneath the plugin name. Alternatively, access the plugin files via FTP or file manager and open the main plugin file (typically wrc-pricing-tables.php or similar) to read the Version header in the plugin comment block.
    Affected if The version number is 2.3.7 or lower.
  3. Verify the plugin is active
    In the WordPress admin Plugins list, check if the plugin has an 'Active' status under the plugin name.
    Affected if The plugin is currently active.
  4. Test for unauthenticated admin access
    Send a direct HTTP request to common admin AJAX endpoints or plugin-specific action URLs without providing any authentication credentials (no logged-in session). For this plugin, attempt requests to /wp-admin/admin-ajax.php with plugin-related actions or any endpoint that should require admin privileges.
    Affected if The request completes successfully without returning an authentication error or requiring login.

You are affected if the WRC Pricing Tables plugin version 2.3.7 or lower is installed and active, and unauthenticated users can access admin-level functionality.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper capability checks and authorization verification for all sensitive operations in the plugin; ensure all admin actions require valid nonce tokens and appropriate user capabilities.

Have this fixed 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 help mitigating

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-32293 — 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-32293 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