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

CVE-2024-31936

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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
Cross-Site Request Forgery (CSRF) vulnerability in AyeCode Ltd UsersWP.This issue affects UsersWP: from n/a before 1.2.6.

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

Cross-Site Request Forgery (CSRF) vulnerability in UsersWP plugin allows attackers to force authenticated users to perform unwanted actions by tricking them into submitting malicious requests to the application.

MitigationUpdate UsersWP to version 1.2.6 or later which includes anti-CSRF token validation. Implement WordPress nonce checks on all state-changing forms and AJAX endpoints.

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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. Confirm UsersWP plugin is installed
    Check WordPress plugin directory for /userswp/ folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if UsersWP plugin is not found in the installation
  2. Identify installed UsersWP version
    View the plugin version in WordPress admin (Plugins > Installed Plugins > UsersWP) or read the main plugin file header in wp-content/plugins/userswp/userswp.php
    Affected if Cannot determine version or version is below 1.2.6
  3. Verify plugin is active
    Check if UsersWP is enabled in WordPress admin under Plugins > Installed Plugins (plugin status must be 'Active')
    Affected if UsersWP is installed but not currently active
  4. Compare version to vulnerability range
    Compare your installed version number to the affected range: versions prior to 1.2.6 are vulnerable
    Affected if Installed version is 1.2.5 or lower, or any version below 1.2.6

You are affected if UsersWP plugin is installed, active, and running at version 1.2.5 or lower (any version below 1.2.6).

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 UsersWP to version 1.2.6 or later which includes anti-CSRF token validation. Implement WordPress nonce checks on all state-changing forms and AJAX endpoints.

Recommended fix Moderate confidence

1.2.6 or later

  1. Upgrade the UsersWP plugin to version 1.2.6 or later to remediate the CSRF vulnerability

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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