dbcve.org
Profile BuilderWordPress extension · Cozmoslabs

CVE-2024-22142

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-13
Fix available
A fix is available. Upgrade to after 3.10.0 or later.
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Cozmoslabs Profile Builder Pro allows Reflected XSS.This issue affects Profile Builder Pro: from n/a through 3.10.0.

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

Profile Builder Pro plugin versions up to 3.10.0 contain a reflected cross-site scripting (XSS) vulnerability where user-supplied input is not properly sanitized before being rendered in web pages. This allows attackers to inject malicious JavaScript through crafted URLs that get reflected back to the victim.

MitigationUpdate Profile Builder Pro to the latest version which includes proper input validation and output encoding. If no update is available, implement web application firewall rules to block malicious URL parameters.

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
Profile BuilderWordPress extension
Affected:<= 3.10.0

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 Profile Builder Pro is installed
    Log into your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Profile Builder Pro' or 'Cozmoslabs Profile Builder' in the list of active plugins.
    Affected if The plugin is not found in the installed plugins list, then this CVE does not apply.
  2. Check installed version number
    In the WordPress admin, go to Plugins > Installed Plugins. Find Profile Builder Pro and locate the version number displayed beneath the plugin name.
    Affected if The displayed version number is 3.10.0 or lower, indicating a vulnerable version.
  3. Confirm version is within affected range
    Compare your installed version against the affected range: versions 3.10.0 and below.
    Affected if Your version is 3.10.0 or any version lower than 3.10.0, meaning the plugin is vulnerable to reflected XSS.
  4. Identify potential reflection points
    Review your website for URL parameters that might reflect user input back into pages, such as query strings in profile pages or form submission redirects.
    Affected if URL parameters are reflected in page content without sanitization and your plugin version is 3.10.0 or lower.

You are affected if Profile Builder Pro (Cozmoslabs Profile Builder) is installed and the installed version is 3.10.0 or lower.

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 3.10.0
Interim mitigation

Update Profile Builder Pro to the latest version which includes proper input validation and output encoding. If no update is available, implement web application firewall rules to block malicious URL parameters.

Recommended fix Moderate confidence

Profile Builder Pro version 3.10.1 or later (latest available version)

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate Profile Builder Pro (by Cozmoslabs) in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, clear any server-side and browser caches
  6. 6. Test the plugin functionality to ensure the update was successful
  7. 7. Verify the XSS vulnerability is resolved by confirming user input is properly sanitized in affected areas

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

Fix this in Profile Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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