Missing AuthorizationWeakness · CWE-862

CVE-2025-47556

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 QuanticaLabs CSS3 Compare Pricing Tables for WordPress css3_web_pricing_tables_grids allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CSS3 Compare Pricing Tables for WordPress: from n/a through <= 11.6.

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

A missing authorization vulnerability in QuanticaLabs CSS3 Compare Pricing Tables WordPress plugin (css3_web_pricing_tables_grids) allows attackers to exploit incorrectly configured access control security levels, potentially accessing or modifying pricing table configurations without proper authentication or authorization checks.

MitigationUpdate the plugin to version 11.7 or later; review and enforce proper capability checks on all admin actions and AJAX endpoints to ensure only authorized users can access sensitive functions.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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. Verify the plugin is installed
    Check if the QuanticaLabs CSS3 Compare Pricing Tables plugin (css3_web_pricing_tables_grids) exists in your WordPress wp-content/plugins/ directory or is listed in Plugins > Installed Plugins in the WordPress admin dashboard.
    Affected if The plugin is present and active in the WordPress installation.
  2. Identify the installed version
    Open the main plugin file (usually css3_web_pricing_tables_grids.php) and locate the Version header comment at the top, or check the plugin version displayed in the WordPress admin Plugins list.
    Affected if The installed version is lower than 11.7.
  3. Test unauthenticated AJAX access
    Send a direct HTTP request to /wp-admin/admin-ajax.php with typical plugin action names (such as ptg_save_config, ptg_delete_table, or similar pricing table related actions) without providing any authentication cookies or credentials.
    Affected if The AJAX endpoint returns a successful response instead of requiring authentication (401/403 error).
  4. Inspect admin function capability checks
    Examine the plugin PHP files in the includes or classes directory for admin action handlers and AJAX callbacks; search for current_user_can() or similar WordPress capability checks to verify they are present and correctly configured on functions that modify pricing table configurations.
    Affected if No capability checks are found, or checks are missing on functions that save/delete pricing table configurations.
  5. Check for insecure direct object references
    Review plugin PHP code for parameters that accept pricing table IDs or configuration IDs directly in requests without validating ownership or user permissions, such as ?table_id= or ?config_id= in AJAX or admin form submissions.
    Affected if Parameters are accepted without ownership verification or permission checks.

Your environment is affected if the QuanticaLabs CSS3 Compare Pricing Tables plugin is installed, the version is below 11.7, and AJAX endpoints or admin functions can be accessed or manipulated without proper authentication or capability verification.

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

Update the plugin to version 11.7 or later; review and enforce proper capability checks on all admin actions and AJAX endpoints to ensure only authorized users can access sensitive functions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2025-47556 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