CVE-2024-51637
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 sroyalty Admin SMS Alert admin-sms-alert allows Stored XSS.This issue affects Admin SMS Alert: from n/a through <= 1.1.0.
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 sroyalty Admin SMS Alert plugin allows authenticated attackers to inject malicious scripts via stored XSS. By tricking a logged-in administrator into visiting a crafted page, attackers can perform unintended actions on the admin-sms-alert plugin and embed malicious JavaScript that executes when other admins view the affected interface.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Locate the sroyalty Admin SMS Alert plugin filesCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'sroyalty-admin-sms-alert' or similar variation containing 'sroyalty' and 'sms-alert'Affected if The plugin folder exists in the plugins directory
-
Identify the installed plugin versionOpen the main plugin PHP file (usually plugin-name.php) and look for version comments or a version constant in the plugin headerAffected if The version number found is any version of this plugin, as no fixed version was specified in the advisory
-
Confirm plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify the sroyalty Admin SMS Alert plugin is activatedAffected if The plugin is listed as active in the WordPress plugins screen
-
Identify vulnerable plugin endpointsExamine the plugin PHP files for form handlers and AJAX actions that lack anti-CSRF token validation (look for missing wp_verify_nonce or check_ajax_referer calls)Affected if Forms or AJAX actions in the plugin process requests without validating CSRF tokens
-
Check for stored XSS injection pointsReview the plugin code for input handling functions that store user-supplied data (likely in options, SMS templates, or admin settings) without proper sanitization (sanitize_text_field, esc_html, esc_attr) or output escapingAffected if User-controllable data from forms can be stored and displayed without escaping in admin pages
You are affected if the sroyalty Admin SMS Alert plugin is installed and active in your WordPress environment, as the CSRF vulnerability allows authenticated attackers to inject stored XSS that executes when administrators view the plugin interface.
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 dataImplement anti-CSRF tokens on all state-changing forms and AJAX actions in the plugin, combined with proper input sanitization and output escaping to prevent the stored XSS component.
- Consultation2.0 h
- Implementation6.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51637 — 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-51637 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