dbcve.org
CiviWordPress extension · Uxper

CVE-2024-13773

HIGH · 7.5 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to after 2.1.4 or later.
See remediation →
84/100
Remediation priority · High
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 Sensitive Information Exposure in all versions up to, and including, 2.1.4 via hard-coded credentials. This makes it possible for unauthenticated attackers to extract sensitive data including LinkedIn client and secret keys.

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 contains hard-coded LinkedIn OAuth credentials (client ID and secret) embedded in the source code. Unauthenticated attackers can directly access these credentials, potentially allowing them to authenticate as the affected application to LinkedIn's API and access linked data or perform actions on behalf of the compromised application.

MitigationRemove all hardcoded credentials from the theme codebase and replace with secure storage mechanisms such as environment variables or WordPress configuration constants. Immediately rotate the exposed LinkedIn client ID and secret to prevent continued unauthorized access.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Locate the Civi theme files
    Check your WordPress installation's wp-content/themes directory for a folder named 'civi' or 'uxper-civi'. If using Civi as a plugin, check wp-content/plugins for a Civi-related plugin directory.
    Affected if The Civi theme or plugin directory exists in your WordPress installation
  2. Identify the installed version
    Open the style.css file in the Civi theme folder and look for the 'Version:' comment in the file header, or check the main plugin file if installed as a plugin for the version declaration.
    Affected if The version listed is 2.1.4 or lower
  3. Search for hardcoded LinkedIn client ID
    Use grep, grep -r, or your IDE's search function to find the literal string pattern 'linkedin' and 'client_id' or 'clientId' within the Civi theme/plugin directory. Focus on PHP files.
    Affected if Hardcoded LinkedIn client ID strings are found in source files
  4. Search for hardcoded LinkedIn client secret
    Search within the Civi directory for strings matching 'linkedin' combined with 'client_secret', 'clientSecret', or 'secret'. Examine any found files closely.
    Affected if Hardcoded LinkedIn client secret strings are found in source files
  5. Inspect OAuth configuration files
    Examine files named linkedin.php, oauth.php, api.php, or config.php within the Civi theme/plugin folder. Look for defined constants or variables containing long alphanumeric strings that could be OAuth credentials.
    Affected if OAuth-related files contain exposed credential strings

Your environment is affected if the Civi theme or plugin is installed with version 2.1.4 or lower AND hardcoded LinkedIn OAuth credentials are present in the source code files.

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.

From vendor data
Upgrade available Upgrade to a release after 2.1.4
Interim mitigation

Remove all hardcoded credentials from the theme codebase and replace with secure storage mechanisms such as environment variables or WordPress configuration constants. Immediately rotate the exposed LinkedIn client ID and secret to prevent continued unauthorized access.

Fix this in Civi 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 the upgrade done

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-13773 — 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-13773 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