BloomWordPress extension · Elegantthemes
CVE-2016-11003
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 Elegant Themes Bloom plugin before 1.1.1 for WordPress has privilege escalation.
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 confidenceThe Elegant Themes Bloom plugin before version 1.1.1 for WordPress contains a privilege escalation vulnerability that allows authenticated users to elevate their permissions beyond what they should normally have, potentially gaining administrator-level access to the WordPress site.
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
BloomWordPress extension
< 1.1.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Bloom plugin is installedLog into WordPress admin panel, navigate to Plugins > Installed Plugins, locate the Bloom plugin by Elegant Themes, and confirm it appears in the list.Affected if Bloom plugin is present and active on the WordPress site
-
Check installed Bloom versionIn the Plugins list, look at the version number displayed under the Bloom plugin name, or open wp-content/plugins/bloom/bloom.php and locate the 'Version:' header in the plugin comment block.Affected if The version is displayed as anything lower than 1.1.1 (for example: 1.0.0, 1.0.1, 1.1.0)
-
Confirm authenticated user access existsNavigate to Users > All Users in the WordPress admin panel. Check if there are any user accounts with roles below Administrator (such as Editor, Author, Contributor, or Subscriber), or verify that User Registration is enabled in Settings > General.Affected if The site has at least one non-administrative user account or allows user registration, which provides the authenticated context needed to exploit the privilege escalation
-
Inspect plugin file for vulnerable functionUsing a file manager or FTP, open wp-content/plugins/bloom/bloom.php and search for functions related to permission handling or user role modification. The vulnerable code allows authenticated users to manipulate their capability levels.Affected if The Bloom plugin file contains code that processes user permission updates without proper administrative authorization checks
The environment is affected if the Bloom plugin is installed with any version prior to 1.1.1 and the site has at least one authenticated user account (non-admin or newly registered) that could trigger the privilege escalation flaw.
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 data1.1.1
Update the Bloom plugin to version 1.1.1 or later to remediate this vulnerability. Ensure all user roles and permissions are reviewed after the update.
Fix this in Bloom
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-11003 — 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-2016-11003 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