Profile BuilderWordPress extension · Cozmoslabs
CVE-2015-9337
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 · uneditedThe profile-builder plugin before 2.1.4 for WordPress has no access control for activating or deactivating addons via AJAX.
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 confidenceThe profile-builder WordPress plugin before version 2.1.4 lacks proper access control on AJAX endpoints that handle addon activation and deactivation. This allows any user (with network access to the WordPress admin-ajax.php endpoint) to activate or deactivate plugin addons without authentication or proper authorization checks, effectively enabling unauthorized modification of the plugin's configuration.
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
< 2.1.4CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Profile Builder plugin is installedCheck the WordPress plugins directory for the profile-builder folder, or query the wp_plugins table for 'profile-builder' or 'Cozmoslabs Profile Builder' entryAffected if The plugin folder exists in /wp-content/plugins/ or is found in the plugins database table
-
Determine installed versionRead the main plugin file (usually profile-builder/index.php or profile-builder.php) and locate the 'Version' header in the plugin comment block, or check via wp-admin > Plugins > Profile BuilderAffected if The version number is lower than 2.1.4 (e.g., 2.1.3, 2.0.x, etc.)
-
Check for vulnerable AJAX handlersInspect the plugin source code for AJAX action handlers related to addon activation/deactivation - look for 'add_action("wp_ajax_"...' calls that handle 'profile_builder_activate_addon' or 'profile_builder_deactivate_addon' or similarAffected if AJAX handlers exist that process addon activation/deactivation requests
-
Verify lack of capability checks on AJAX endpointsExamine the AJAX handler functions identified in step 3 - check if they call current_user_can() or a capability check before processing the addon activation/deactivation requestAffected if No capability check (like current_user_can('manage_options')) is found before processing the addon action, or the check is missing entirely
-
Test endpoint accessibilitySend a POST request to /wp-admin/admin-ajax.php with action parameter such as 'profile_builder_activate_addon' or 'profile_builder_deactivate_addon' without providing authentication cookies or a valid nonceAffected if The request is processed and returns a successful response without requiring authentication (returns 200 OK with addon activation/deactivation success rather than a 403 or requiring login)
The environment is affected if Profile Builder plugin version is below 2.1.4 and the AJAX addon management endpoints can be accessed and processed without authentication or capability verification.
Generated from the published advisory. Verify against your own configuration.
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 data2.1.4
Update the profile-builder plugin to version 2.1.4 or later, which implements proper capability checks and nonce validation on the addon management AJAX endpoints.
Fix this in Profile Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9337 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-9337 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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