dbcve.org
CiviWordPress extension · Uxper

CVE-2024-13771

MEDIUM · 5.9 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to after 2.1.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Civi - Job Board & Freelance Marketplace WordPress Theme plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 2.1.4. This is due to a lack of user validation before changing a password. This makes it possible for unauthenticated attackers to change the password of arbitrary users, including administrators, if the attacker knows the username of the victim.

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 Civi WordPress theme plugin lacks proper user validation in its password change functionality, allowing unauthenticated attackers to reset arbitrary user passwords by simply knowing the target's username. This authentication bypass affects all versions up to 2.1.4 and enables full account takeover of any user account, including administrators.

MitigationUpdate the Civi theme plugin to version 2.1.5 or later where proper authentication validation has been implemented. If immediate update is not possible, consider restricting access to the password reset endpoint or implementing Web Application Firewall rules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CiviWordPress extension
Affected:<= 2.1.4

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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. Identify if the Civi theme plugin is present
    Locate the Civi theme or plugin files in the WordPress installation. This may be in wp-content/themes/civi/ or as a plugin in wp-content/plugins/. Check for directories or files containing 'civi' in the name.
    Affected if The Civi theme or plugin is found in the WordPress installation
  2. Determine the installed version
    Open the main Civi theme/plugin file (often style.css for themes or the main PHP file for plugins) and locate the version declaration in the header comments. Alternatively, check a readme.txt or readme.md file if present.
    Affected if The discovered version is 2.1.4 or lower, or no version information is found (which may indicate an unpatched installation)
  3. Verify the password reset endpoint is accessible
    Test access to the WordPress password reset functionality without authentication. This typically involves accessing the login page or password reset form at the standard WordPress login URL. Confirm that the endpoint accepts a username parameter without requiring prior authentication.
    Affected if The password reset endpoint is accessible without being logged in and accepts username input
  4. Confirm the WordPress site uses the Civi theme
    Access the WordPress admin dashboard and navigate to Appearance > Themes (or Plugins > Installed Plugins) to verify that Civi is the active theme or that the Civi plugin is enabled and active.
    Affected if Civi is the currently active theme or an active plugin

A user is affected if the Civi theme/plugin is installed and active with a version of 2.1.4 or lower, and the WordPress password reset functionality is accessible without authentication.

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
Upgrade available Upgrade to a release after 2.1.4
Interim mitigation

Update the Civi theme plugin to version 2.1.5 or later where proper authentication validation has been implemented. If immediate update is not possible, consider restricting access to the password reset endpoint or implementing Web Application Firewall rules.

Recommended fix Moderate confidence

Civi theme version > 2.1.4 (contact theme developer for exact fixed version)

  1. 1. Check your current Civi theme version by navigating to Appearance > Themes in WordPress admin
  2. 2. If the installed version is 2.1.4 or lower, navigate to Appearance > Themes > Add New > Upload Theme
  3. 3. Download the latest version of the Civi theme from the original source (themeforest.net or the theme developer)
  4. 4. Upload and install the updated theme version
  5. 5. After updating, verify the authentication bypass vulnerability is resolved by ensuring password change endpoints require proper authentication
  6. 6. Consider changing passwords for administrative accounts as a precautionary measure
Caveat Review theme documentation for any template or functionality changes in the new version before deploying to production

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

Fix this in Civi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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