Wp SmsWordPress extension · Veronalabs
CVE-2024-24881
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 Input During Web Page Generation ('Cross-site Scripting') vulnerability in VeronaLabs WP SMS – Messaging & SMS Notification for WordPress, WooCommerce, GravityForms, etc allows Reflected XSS.This issue affects WP SMS – Messaging & SMS Notification for WordPress, WooCommerce, GravityForms, etc: from n/a through 6.5.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 · moderate confidenceA reflected Cross-site Scripting (XSS) vulnerability exists in the VeronaLabs WP SMS WordPress plugin (versions through 6.5.2). The vulnerability allows unauthenticated attackers to inject malicious JavaScript code through vulnerable parameters that are reflected back in the web page without proper sanitization or output encoding. This can lead to session hijacking, credential theft, or defacement when users click crafted malicious links.
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.5.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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP SMS plugin is installedLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'wp-sms' or similar.Affected if The plugin folder exists in the WordPress plugins directory.
-
Check installed version numberIn WordPress admin, find the WP SMS plugin entry in the plugins list and read the version number displayed beneath the plugin name. Alternatively, open the main plugin file (typically wp-sms.php or index.php inside the plugin folder) and look for the 'Version' header in the file comments.Affected if The displayed version number is lower than 6.5.3 (e.g., 6.5.2, 6.5.1, etc.).
-
Confirm plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that WP SMS shows as 'Active' rather than 'Inactive'.Affected if The plugin is active and the version is below 6.5.3.
-
Inspect HTTP response for reflected parametersIf you have access to web server logs or can test safely, make a request to a WP SMS-related URL including a test parameter (e.g., ?test=<script>alert(1)</script>) and examine if that parameter value is reflected verbatim in the response HTML without encoding.Affected if User-supplied parameter values are reflected in the page source without HTML entity encoding (e.g., <script> tags appear unescaped).
You are affected if the WP SMS plugin is installed, active, and running version 6.5.2 or lower.
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.5.3
Update the WP SMS plugin to the latest patched version when available. As an immediate interim measure, implement WAF rules to filter malicious XSS payloads and ensure users do not click untrusted links pointing to the affected application.
6.5.3
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'WP SMS – Messaging & SMS Notification' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 6.5.3 of the plugin
- Verify the update completed successfully to version 6.5.3
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
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24881 — 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-24881 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