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

CVE-2024-11342

MEDIUM · 6.1 CVSS v3.1 Published 2024-11-26
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 Skt NURCaptcha plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.5.0. This is due to missing or incorrect nonce validation in the skt-nurc-admin.php file. This makes it possible for unauthenticated attackers to update settings and 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 · high confidence

The Skt NURCaptcha WordPress plugin up to version 3.5.0 lacks nonce validation in skt-nurc-admin.php, allowing unauthenticated attackers to forge requests that trick administrators into performing unintended actions. Successful exploitation enables setting modifications and stored XSS injection via malicious web scripts.

MitigationUpdate the plugin to version 3.5.1 or later, which should include proper nonce validation. Until patched, avoid clicking untrusted links while logged into the WordPress admin.

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. Verify Skt NURCaptcha plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Skt NURCaptcha' in the installed plugins list, or check the /wp-content/plugins/ directory for a folder named 'skt-nurcaptcha' or similar
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view its details and locate the version number, or inspect the main plugin file (usually skt-nurcaptcha.php or similar in the plugin folder) for the Version header in the plugin comment block
    Affected if The version is 3.5.0 or lower
  3. Locate the vulnerable admin file
    Check for the presence of skt-nurc-admin.php in the plugin directory (typically /wp-content/plugins/skt-nurcaptcha/ or similar folder name)
    Affected if The file skt-nurc-admin.php exists in the plugin folder
  4. Check plugin activation status
    In WordPress admin > Plugins, verify whether the Skt NURCaptcha plugin is activated
    Affected if The plugin is currently activated

If Skt NURCaptcha is installed, activated, and the version is 3.5.0 or lower, the environment is affected by this CSRF vulnerability that can lead to settings changes and stored XSS.

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 the plugin to version 3.5.1 or later, which should include proper nonce validation. Until patched, avoid clicking untrusted links while logged into the WordPress admin.

Recommended fix Moderate confidence

Latest version of Skt NURCaptcha (version higher than 3.5.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Skt NURCaptcha plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, manually download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin settings remain configured as intended

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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