dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-51688

HIGH · 7.1 CVSS v3.1 Published 2024-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in fraudlabspro FraudLabs Pro SMS Verification fraudlabs-pro-sms-verification allows Stored XSS.This issue affects FraudLabs Pro SMS Verification: from n/a through <= 1.10.1.

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 confidence

A CSRF vulnerability in the FraudLabs Pro SMS Verification WordPress plugin (version <= 1.10.1) allows attackers to trick authenticated administrators into submitting malicious requests that result in stored XSS. The lack of anti-CSRF tokens on state-changing forms enables attackers to inject persistent malicious scripts that execute when other users view the affected pages.

MitigationImplement anti-CSRF tokens (nonce validation) on all forms and AJAX actions, and apply proper output escaping for all user-supplied data before rendering to prevent stored XSS.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the FraudLabs Pro SMS Verification plugin files
    Check the wp-content/plugins/ directory for a folder named 'fraudlabs-pro-sms-verification' or similar variant containing 'fraudlabspro' or 'fraud-labs'
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named fraudlabs-pro-sms-verification.php) and locate the 'Version' header comment, or check readme.txt for the version field
    Affected if The version number is 1.10.1 or lower
  3. Confirm the plugin is active
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins, or query the wp_options table for the active_plugins option to check if FraudLabs Pro SMS Verification is enabled
    Affected if The plugin appears in the active plugins list or active_plugins option contains its reference
  4. Inspect admin forms for missing nonce fields
    Examine the plugin's admin PHP files (settings pages, SMS configuration forms) and search for state-changing form submissions (POST requests) that lack wp_nonce_field() or check_admin_referer() calls
    Affected if Forms that modify plugin settings or user data lack anti-CSRF nonce validation tokens
  5. Verify XSS output escaping is missing
    Review the plugin's output functions that render user-supplied data (settings values, SMS content, responses) and check if they use esc_html(), esc_attr(), or similar escaping functions before echoing
    Affected if User-supplied data is echoed without proper escaping functions, allowing stored XSS

If the FraudLabs Pro SMS Verification plugin is installed, active, and version 1.10.1 or lower, and its admin forms lack nonce validation with user data output not escaped, the environment is affected by CVE-2024-51688.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonce validation) on all forms and AJAX actions, and apply proper output escaping for all user-supplied data before rendering to prevent stored XSS.

Recommended fix Moderate confidence

FraudLabs Pro SMS Verification plugin version 1.10.2 or latest available

  1. Check the WordPress plugin repository or FraudLabs Pro official website for the latest version of the FraudLabs Pro SMS Verification plugin
  2. Upgrade the plugin to the latest available version (likely 1.10.2 or higher)
  3. Verify the upgrade was successful by checking the plugins page in WordPress admin
  4. Test that the SMS verification functionality still works correctly after the upgrade
  5. Clear any caching if applicable

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51688 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51688 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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