CVE-2025-47556
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 · uneditedMissing 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 confidenceA 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.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck 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.
-
Identify the installed versionOpen 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.
-
Test unauthenticated AJAX accessSend 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).
-
Inspect admin function capability checksExamine 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.
-
Check for insecure direct object referencesReview 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.
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 dataUpdate 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.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47556 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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