dbcve.org
CiviWordPress extension · Uxper

CVE-2024-13772

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.6.1. This is due to a lack of password randomization and user validation through the fb_ajax_login_or_register and google_ajax_login_or_register actions. This makes it possible for unauthenticated attackers to login as any user as long as they have access to the email.

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 has an authentication bypass vulnerability in the fb_ajax_login_or_register and google_ajax_login_or_register AJAX actions. These functions fail to properly validate user credentials and password randomization, allowing unauthenticated attackers to log in as any user by providing a valid email address.

MitigationUpdate the Civi theme to a version newer than 2.1.6.1. If immediate update is not possible, consider disabling social login features or implementing additional server-side authentication controls.

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. Confirm Civi theme is installed
    Log into WordPress admin and navigate to Appearance > Themes, or check /wp-content/themes/ directory for the civi or uxper-civi folder
    Affected if The Civi theme by Uxper is active or installed on the WordPress site
  2. Identify installed Civi theme version
    Check the style.css file in the theme directory for the 'Version:' header, or view the theme details in WordPress admin under Appearance > Themes
    Affected if The version number listed is 2.1.4 or lower
  3. Check if vulnerable AJAX actions are exposed
    Send a POST request to /wp-admin/admin-ajax.php with action=fb_ajax_login_or_register or action=google_ajax_login_or_register and observe the response
    Affected if The endpoint responds and accepts requests without requiring authentication (returns 200 OK rather than 403 or requiring login)
  4. Verify social login feature is enabled
    Check WordPress admin > Theme Options or Civi theme settings for social login configuration (Facebook/Google login settings)
    Affected if Social login features are enabled and configured in the theme settings

If the Civi theme version is 2.1.4 or lower AND the social login AJAX endpoints are accessible without authentication, the site is affected by this CVE.

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 to a version newer than 2.1.6.1. If immediate update is not possible, consider disabling social login features or implementing additional server-side authentication controls.

Recommended fix Moderate confidence

Civi version 2.1.7 or later (if available)

  1. 1. Check the current installed version of the Civi theme in WordPress (Appearance > Themes).
  2. 2. Visit the official ThemeForest or Theme goods marketplace to obtain the latest version of the Civi theme.
  3. 3. Before upgrading, backup the entire WordPress site including database and files.
  4. 4. If available, test the upgrade in a staging environment first to ensure compatibility with existing content and plugins.
  5. 5. In WordPress admin, navigate to Appearance > Themes and activate a different temporary theme.
  6. 6. Delete the old Civi theme and upload/install the new version from the theme package.
  7. 7. Reconfigure any theme-specific settings and child theme customizations after upgrade.
  8. 8. Verify the authentication bypass vulnerability is fixed by attempting the described attack vector with the fb_ajax_login_or_register or google_ajax_login_or_register actions.
Caveat Review theme documentation for any settings or template changes between versions; child theme customizations may need adjustment

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

Fix this in Civi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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