CVE-2025-66122
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 Design Stylish Price List stylish-price-list allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Stylish Price List: from n/a through <= 7.2.2.
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 confidenceThe Stylish Price List WordPress plugin versions up to 7.2.2 contains a missing authorization vulnerability where access control security levels are incorrectly configured, potentially allowing unauthenticated or lower-privileged users to access administrative functionality or sensitive data that should require higher privileges.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Stylish Price List plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'Stylish Price List' or check the file /wp-content/plugins/stylish-price-list/ for existenceAffected if The plugin directory exists in the WordPress plugins folder and the plugin is active
-
Check installed plugin versionIn WordPress admin_plugins list, find the Stylish Price List plugin and read the version number displayed below the plugin name; alternatively, open /wp-content/plugins/stylish-price-list/readme.txt and check the 'Stable tag' or /wp-content/plugins/stylish-price-list/stylish-price-list.php and find the 'Version' header commentAffected if The version is 7.2.2 or lower (any version up to and including 7.2.2)
-
Identify exposed admin AJAX actionsInspect the main plugin PHP file for do_action or add_action calls registering AJAX endpoints (search for 'wp_ajax_' or 'wp_ajax_nopriv_' hooks); also check for any registered REST API routes by searching for 'register_rest_route'Affected if AJAX or REST endpoints are registered that handle administrative functions without capability checks or with incorrect permission checks
-
Test for unauthenticated access to plugin functionsAttempt to access plugin admin pages or known plugin action URLs while logged out (as an unauthenticated user) or as a low-privileged user (subscriber); check if the plugin responds without redirecting to login or returning a permission denied errorAffected if The plugin allows unauthenticated or low-privilege users to access administrative functionality or execute actions that should require higher privileges
A user is affected if the Stylish Price List plugin version is 7.2.2 or lower and the plugin exposes administrative functionality or sensitive data to unauthenticated users or lower-privileged roles without proper authorization checks.
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 Stylish Price List plugin to the latest version (7.3 or later) which should include proper authorization checks; if no update is available, review the plugin's access control configuration and consider disabling the plugin until a patch is released.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66122 — 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-66122 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