CVE-2025-49915
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 · uneditedImproper 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.5.
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 · high confidenceSQL Injection vulnerability in Cozy Vision SMS Alert Order Notifications (sms-alert) plugin allows attackers to inject malicious SQL commands via unsanitized user input in order notification parameters. The vulnerability affects all versions through 3.8.5 and could allow complete database compromise including exfiltration of sensitive customer and order data.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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.
-
Identify if SMS Alert plugin is installedCheck your WordPress plugins directory for the 'sms-alert' folder at wp-content/plugins/sms-alert/ or view the installed plugins in WordPress admin under Plugins > Installed PluginsAffected if The SMS Alert Order Notifications plugin by Cozy Vision is present in the plugins directory
-
Check installed plugin versionView the plugin file header (usually in sms-alert/readme.txt or sms-alert/sms-alert.php) to find the Version field, or check the plugin details in WordPress admin plugins listAffected if The installed version is 3.8.5 or any version prior to the patched release
-
Verify order notification configurationNavigate to SMS Alert settings in WordPress admin (usually under WooCommerce > SMS Alert or Settings > SMS Alert) and examine the order notification parameters for any custom fields that accept user inputAffected if Order notification settings contain custom parameters or fields that accept user-supplied input without visible sanitization indicators
-
Inspect database for suspicious activityReview database tables (particularly those related to orders and SMS logs) for unusual query patterns, unexpected data, or signs of data exfiltration by checking MySQL slow query logs or general logs if enabledAffected if Unusual SQL queries appear in logs or unexpected data exists in order-related tables indicating potential exploitation
You are affected if the Cozy Vision SMS Alert plugin versions through 3.8.5 is installed and order notification parameters accept unsanitized user input.
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 a patched version of SMS Alert Order Notifications that implements proper input sanitization and uses parameterized queries/prepared statements for all database operations involving user-supplied data.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49915 — 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-49915 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