Wp SmsWordPress extension · Veronalabs
CVE-2024-30454
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in VeronaLabs WP SMS.This issue affects WP SMS: from n/a through 6.6.2.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the VeronaLabs WP SMS WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (such as sending SMS messages or modifying plugin settings) by crafting malicious requests that the victim's browser automatically submits.
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.6.3CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP SMS' by Veronalabs, or check the file /wp-content/plugins/wp-sms/wp-sms.php existsAffected if Plugin is installed and active
-
Check installed versionIn WordPress admin Plugins page, find WP SMS and view the version number; alternatively, check the 'Version' field in the plugin header comment in /wp-content/plugins/wp-sms/wp-sms.phpAffected if Version is less than 6.6.3
-
Confirm admin authentication requirementUnderstand that this CSRF vulnerability requires a logged-in administrator to unknowingly submit a malicious request (e.g., via a crafted link or page)Affected if Authenticated admin users exist and the plugin handles sensitive actions without anti-CSRF tokens
If WP SMS version is below 6.6.3 and the plugin is active with authenticated administrator access, the environment is vulnerable to CSRF attacks.
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.6.3
Apply the latest version of WP SMS (6.6.3 or higher) which includes anti-CSRF token validation and SameSite cookie attributes; alternatively, disable the plugin until patched.
WP SMS 6.6.3
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the WP SMS plugin by VeronaLabs
- 4. If an update is available, click 'Update Now' to upgrade to version 6.6.3 or later
- 5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload version 6.6.3 or higher if automatic update is not available
- 6. After updating, verify the plugin version shows 6.6.3 or newer
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
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30454 — 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-30454 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