Wp SmsWordPress extension · Veronalabs
CVE-2024-43331
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 VeronaLabs WP SMS.This issue affects WP SMS: from n/a through 6.9.3.
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 confidenceThe WP SMS plugin by VeronaLabs versions up to 6.9.3 contains a missing authorization vulnerability, allowing attackers to bypass access controls and perform actions that should require proper authentication and privileges. The critical CVSS 9.8 score indicates unauthenticated attackers can likely access sensitive functionality.
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
Wp SmsWordPress extension
< 6.9.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP SMS plugin is installedNavigate to WordPress admin > Plugins and look for 'WP SMS' by Veronalabs in the installed plugins listAffected if WP SMS plugin is not installed on the WordPress site
-
Check installed WP SMS versionIn Plugins list, locate WP SMS and note the version number displayed, or check the plugin header in wp-content/plugins/wp-sms/wp-sms.php for the 'Version' constantAffected if Installed version is 6.9.3 or lower (less than 6.9.4)
-
Confirm plugin is activeIn WordPress admin > Plugins, check if WP SMS shows as 'Active' statusAffected if Plugin is active and version is below 6.9.4
-
Review SMS sending logs for unauthorized activityIn WP SMS settings, access the SMS logs or sent messages history and look for SMS activity originating from unknown or unexpected phone numbers, timestamps outside business hours, or messages you did not authorizeAffected if SMS logs show messages sent without legitimate admin authorization
-
Check for unexpected administrator accountsIn WordPress admin > Users, review the user list for any new or unknown administrator accounts that may have been created through exploited functionalityAffected if Unexpected administrator accounts exist that were not created by legitimate admins
A WordPress site running WP SMS version 6.9.3 or lower with the plugin active is affected by this missing authorization vulnerability and should be investigated for signs of unauthorized SMS activity or account creation.
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.
dbcve · scoped6.9.4
Update WP SMS to the latest version once available, or disable the plugin until a patched version is released. Restrict plugin access settings and monitor for unauthorized SMS sending activity.
6.9.4
- Update the WP SMS plugin to version 6.9.4 or later through the WordPress admin dashboard under Plugins > Installed Plugins
- Navigate to Plugins > Add New > Upload (or use automatic update) and install version 6.9.4
- After updating, verify the plugin version shows 6.9.4 in the plugins list
- Test core WP SMS functionality (sending SMS, subscriber management) to ensure the update did not break legitimate operations
- Review user roles and capabilities to confirm authorization controls are functioning as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Sms
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43331 — 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-2024-43331 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