dbcve.org
Sms Alert Order NotificationsWordPress extension · Cozyvision

CVE-2025-26988

HIGH · 7.5 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to 3.7.9 or later.
See remediation →
84/100
Remediation priority · High
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.7.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 confidence

SQL Injection vulnerability in the Cozy Vision SMS Alert WordPress plugin's order notification functionality. Attackers can inject malicious SQL commands through unsanitized input parameters in order notification processing, potentially allowing unauthorized data access or manipulation of the database.

MitigationUpdate to the latest patched version of SMS Alert when available. As an immediate workaround, restrict access to the affected endpoints and implement web application firewall rules to detect and block SQL injection patterns.

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.7.9

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 checks

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

  1. Check the installed plugin version via WordPress admin
    Log into the WordPress dashboard, go to Plugins, and locate the Cozyvision Sms Alert (or SMS Alert) plugin. Note the version number displayed under the plugin name.
    Affected if The version number shown is below 3.7.9 (any version starting with 3.7.8, 3.7.7, etc., or earlier)
  2. Check the plugin version via file inspection
    Access the WordPress plugins directory on the server (commonly wp-content/plugins/sms-alert or similar). Open the main plugin PHP file and locate the Version header in the plugin comment block.
    Affected if The Version field in the plugin file header shows a version below 3.7.9
  3. Confirm order notification functionality is active
    In the WordPress admin panel, navigate to the SMS Alert plugin settings and check whether the order notification feature is enabled. This is typically found under WooCommerce or SMS Alert settings pages.
    Affected if Order notifications are enabled and the plugin version is below 3.7.9
  4. Identify if the plugin handles WooCommerce orders
    Check if WooCommerce is installed and if the SMS Alert plugin is configured to send notifications for order status changes, checkout, or other order events.
    Affected if The plugin is configured to process WooCommerce order notifications and the installed version is below 3.7.9

You are affected if the Cozyvision SMS Alert plugin is installed with any version below 3.7.9 and the order notification feature is in use.

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.7.9 or later
Fixed in 3.7.9
Interim mitigation

Update to the latest patched version of SMS Alert when available. As an immediate workaround, restrict access to the affected endpoints and implement web application firewall rules to detect and block SQL injection patterns.

Recommended fix High confidence

3.7.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Sms Alert Order Notifications' by Cozy Vision
  4. Click 'Update now' if an update is available, or manually upload version 3.7.9
  5. Verify the plugin version shows 3.7.9 after updating
  6. Test that the SMS notification functionality works correctly

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26988 — 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-26988 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