dbcve.org
Sms Alert Order NotificationsWordPress extension · Cozyvision

CVE-2025-47682

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-12
Fix available
A fix is available. Upgrade to 3.8.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Cozy Vision SMS Alert Order Notifications sms-alert allows SQL Injection.This issue affects SMS Alert Order Notifications: from n/a through <= 3.8.1.

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 confidence

SQL injection vulnerability in Cozy Vision's SMS Alert Order Notifications plugin (sms-alert) allows attackers to inject malicious SQL queries via unsanitized input in the plugin's order notification functionality. The vulnerability stems from improper neutralization of special elements in SQL commands, enabling remote attackers to manipulate database queries.

MitigationUpgrade to version 3.8.2 or later which contains the security fix. If immediate patching is not possible, restrict access to the affected endpoints and implement web application firewall rules to block SQL injection attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sms Alert Order NotificationsWordPress extension
Affected:< 3.8.2

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Cozy Vision SMS Alert plugin is installed
    Check your WordPress installation's plugin directory for the 'sms-alert' plugin folder or search for 'Cozyvision' in the WordPress admin plugins page
    Affected if The plugin folder 'sms-alert' exists in wp-content/plugins/ or the plugin appears in the WordPress plugin list
  2. Determine the installed version of the SMS Alert plugin
    Open the main plugin file (typically sms-alert/sms-alert.php) and locate the version number in the plugin header comment, or check the version in wp-content/plugins/sms-alert/readme.txt
    Affected if The version number found is lower than 3.8.2 (e.g., 3.8.1, 3.8.0, earlier versions)
  3. Verify the order notification functionality is enabled
    Access the plugin settings in the WordPress admin panel under SMS Alert settings and check if order notification features are active or configured for any WooCommerce or e-commerce orders
    Affected if Order notifications are enabled and configured to trigger on order events
  4. Check access to order notification endpoints
    Review your web server logs or firewall logs for requests to the plugin's order notification handlers (typically endpoints processing order-related AJAX calls or webhook callbacks)
    Affected if The plugin endpoints are publicly accessible without additional authentication layers and show unusual query patterns
  5. Inspect database query logs for the SMS Alert plugin
    Enable query logging or review existing database logs for SQL queries originating from the sms-alert plugin, looking for unexpected or suspicious SQL patterns in order notification processing
    Affected if SQL queries contain unexpected parameters, UNION statements, or unusual data that suggests injection attempts have been made

Your environment is affected if the Cozy Vision SMS Alert Order Notifications plugin (sms-alert) is installed with a version lower than 3.8.2 AND the order notification functionality is active and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.8.2 or later
Fixed in 3.8.2
Interim mitigation

Upgrade to version 3.8.2 or later which contains the security fix. If immediate patching is not possible, restrict access to the affected endpoints and implement web application firewall rules to block SQL injection attempts.

Recommended fix High confidence

3.8.2

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'SMS Alert Order Notifications' plugin
  4. Click 'Update now' to upgrade to the latest version
  5. Verify the plugin shows version 3.8.2 after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sms Alert Order Notifications Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47682 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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