CVE-2026-32373
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.9.0.
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 confidenceMissing authorization vulnerability in Cozy Vision SMS Alert (sms-alert) plugin allows attackers to access or manipulate SMS order notification settings due to incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to sensitive order notification functionality.
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.
-
Confirm SMS Alert plugin is installedCheck for the presence of the sms-alert plugin directory in wp-content/plugins/ and identify the installed version from the plugin header or readme fileAffected if The plugin is installed and the version falls within the affected range or is unknown/unpatched
-
Identify plugin versionLocate the version string in the plugin's main PHP file (plugin header comment) or readme.txtAffected if The installed version cannot be verified as patched or is older than the patched version
-
Verify access to SMS notification settingsAttempt to access the SMS order notification settings panel or endpoint while logged in as a non-administrator user (subscriber, editor, author, or contributor role)Affected if Settings are accessible or modifiable without admin-level permissions
-
Check capability requirements on AJAX actionsInspect plugin source code for AJAX handlers related to order notifications and verify if current_user_can() or similar permission checks are presentAffected if AJAX endpoints lack proper capability verification and can be triggered by any authenticated user
-
Review nonce validation on settings saveExamine the code handling SMS alert configuration saves to determine if nonce verification is implementedAffected if Settings can be modified without valid nonce tokens or proper authorization checks
-
Test order notification trigger endpointsSubmit a test order notification request using a low-privilege user session to verify if the plugin rejects unauthorized accessAffected if Order notification settings can be viewed or altered by users lacking administrative capabilities
The environment is affected if the SMS Alert plugin is installed and non-administrator users can access or modify SMS order notification settings 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 dataImplement proper authentication and authorization checks (capability/permission verification) on all SMS Alert order notification endpoints and functions. Restrict access to administrative users only.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32373 — 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-32373 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