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

CVE-2024-10726

MEDIUM · 6.1 CVSS v3.1 Published 2024-11-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The Friendly Functions for Welcart plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.4. This is due to missing nonce validation on the settings update functionality. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

The Friendly Functions for Welcart WordPress plugin lacks nonce validation on its settings update functionality, allowing unauthenticated attackers to forge administrative requests. Successful exploitation could allow injection of malicious scripts that execute when administrators access affected settings pages.

MitigationUpdate to a patched version when available; temporarily disable the plugin if no update exists; implement manual nonce validation on all settings-related actions until patched.

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
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 checks

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

  1. Confirm plugin installation
    Navigate to WordPress admin > Plugins and verify 'Friendly Functions for WelCart' is installed and active
    Affected if Plugin is installed and active with no version patched against this CVE
  2. Identify installed version
    In Plugins list, locate 'Friendly Functions for WelCart' and note the version number displayed under the plugin name; alternatively, check the plugin header in /wp-content/plugins/friendly-functions-for-welcart/friendly-functions-for-welcart.php
    Affected if Installed version is lower than the patched version released for CVE-2024-10726
  3. Verify settings page accessibility
    Attempt to access the plugin settings page via WordPress admin (typically under WelCart > Friendly Functions or Settings > Friendly Functions), or inspect if the plugin registers any settings-related admin menu items
    Affected if Plugin settings page exists and is accessible to administrator accounts
  4. Inspect nonce validation in settings handler
    Examine the plugin PHP file for settings update actions: search for 'update_option', 'settings_fields', or form handling code; verify that wp_nonce_field() or check_admin_referer() is called on settings save requests
    Affected if No nonce verification is found on settings update functionality (the vulnerable condition)
  5. Review option handling for script injection risk
    In the plugin code, locate where settings values are saved and output; check if user-supplied values are sanitized before storage and before display on admin pages
    Affected if Settings values are saved without proper sanitization and displayed without escaping, enabling stored XSS

User is affected if the plugin is installed, the installed version predates the CVE-2024-10726 patch, and the settings functionality lacks nonce validation enabling forged admin requests with script injection.

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

Update to a patched version when available; temporarily disable the plugin if no update exists; implement manual nonce validation on all settings-related actions until patched.

Recommended fix Moderate confidence

Latest version newer than 1.2.4 (check wordpress.org for current stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Friendly Functions for Welcart' plugin
  4. Check if an update is available for the plugin
  5. If update available, click 'Update Now' to install the latest version
  6. If no update shown, manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After update, verify settings functionality works correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10726 — 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-10726 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