dbcve.org
Profile BuilderWordPress extension · Cozmoslabs

CVE-2016-10911

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-21
Fix available
A fix is available. Upgrade to 2.4.2 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
The profile-builder plugin before 2.4.2 for WordPress has multiple XSS issues.

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 profile-builder WordPress plugin before version 2.4.2 contains multiple Cross-Site Scripting (XSS) vulnerabilities. These allow unauthenticated attackers to inject malicious scripts into pages viewed by users, potentially leading to session hijacking or credential theft.

MitigationUpdate the profile-builder plugin to version 2.4.2 or later to obtain the XSS patches.

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:< 2.4.2

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.0/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 plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a profile-builder folder
    Affected if The Cozmoslabs Profile Builder plugin is present on the WordPress site
  2. Check installed plugin version
    In WordPress admin, find Profile Builder in the plugins list and read the version number displayed below the plugin name, or check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The displayed version number is lower than 2.4.2 (for example: 2.4.1, 2.4.0, 2.3.x, etc.)
  3. Confirm plugin is active
    In WordPress admin Plugins page, verify that Profile Builder shows as 'Active' under the plugin status column
    Affected if The plugin is activated and running on the site

If Profile Builder plugin is installed, active, and its version is below 2.4.2, the environment is affected by this CVE and vulnerable to XSS attacks.

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 2.4.2 or later
Fixed in 2.4.2
Interim mitigation

Update the profile-builder plugin to version 2.4.2 or later to obtain the XSS patches.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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