CVE-2026-54847
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 · uneditedUnauthenticated Broken Access Control in Stylish Cost Calculator <= 8.3.9 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 confidenceUnauthenticated broken access control vulnerability in Stylish Cost Calculator plugin version 8.3.9 and below allows unauthenticated attackers to access sensitive functionality or data that should require authentication and proper 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Stylish Cost Calculator plugin is installedLocate the plugin directory - typically at /wp-content/plugins/stylish-cost-calculator/ and check for the main PHP file containing the plugin header with version informationAffected if The plugin directory exists and contains the Stylish Cost Calculator files
-
Determine the installed plugin versionOpen the main plugin file (usually stylish-cost-calculator.php) and locate the 'Version' field in the plugin header comment block at the top of the fileAffected if The version number displayed is 8.3.9 or lower (any version from the plugin's initial release up to and including 8.3.9)
-
Confirm unauthenticated AJAX endpoint accessibilitySend a GET or POST request to the plugin's admin-ajax.php endpoint used by Stylish Cost Calculator without providing any authentication credentials (typical endpoint pattern: /wp-admin/admin-ajax.php?action=stylish_cost_calculator_*). Use a tool like curl to test: curl -s -o /dev/null -w '%{http_code}' https://yourdomain.com/wp-admin/admin-ajax.php?action=stylish_cost_calculator_...Affected if The server returns a successful HTTP response (200 OK) instead of redirecting to login (302) or returning 401/403 authentication required error
You are affected if Stylish Cost Calculator version 8.3.9 or lower is installed AND the admin AJAX endpoints respond without requiring authentication.
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 dataUpgrade to the latest version of Stylish Cost Calculator which contains proper authentication and authorization controls. If no patch is available, restrict access to the plugin's admin AJAX endpoints via server-side configuration or temporarily disable the plugin.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54847 — 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-2026-54847 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