CVE-2025-66086
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 Cozy Vision SMS Alert Order Notifications sms-alert allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SMS Alert Order Notifications: from n/a through <= 3.8.8.
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 confidenceThis is a missing authorization (IDOR/broken access control) vulnerability in the Cozy Vision SMS Alert Order Notifications WordPress plugin. The plugin fails to properly enforce authorization checks on order notification endpoints, allowing unauthenticated or unauthorized users to access sensitive order notification functionality due to incorrectly configured access control security levels.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Confirm SMS Alert plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'SMS Alert Order Notifications' or 'Cozy Vision SMS Alert' plugin. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'sms-alert' in the name.Affected if The plugin is present in the WordPress installation
-
Identify installed plugin versionIn WordPress admin > Plugins, find the SMS Alert plugin and read the version number displayed below the plugin name. Alternatively, check the main plugin PHP file for a 'Version' header comment.Affected if The installed version is 3.8.8 or lower
-
Verify order notification endpoints are accessibleTest access to common SMS Alert order notification endpoints such as /?smsalert=order-notify or /wp-json/smsalert/v1/order-notify using a tool like curl or a browser (while logged out). Compare HTTP response codes.Affected if Endpoints return 200 OK or sensitive data without requiring authentication
-
Check access control security level configurationIn WordPress admin, navigate to SMS Alert settings > General Settings > Access Control and verify the 'Security Level' or 'Authorization' setting. The vulnerability stems from incorrectly configured security levels.Affected if Security level is set to 'Public' or 'Guest' or is misconfigured to allow unauthenticated access
A user is affected if the SMS Alert plugin version is 3.8.8 or lower AND the order notification endpoints are accessible without authentication due to misconfigured access control settings.
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 the SMS Alert plugin (beyond 3.8.8) which contains proper authorization checks, and review and configure appropriate access control settings for order notification endpoints.
- Consultation3.0 h
- Implementation3.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66086 — 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-66086 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