CVE-2025-8572
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 Truelysell Core plugin for WordPress is vulnerable to privilege escalation in versions less than, or equal to, 1.8.7. This is due to insufficient validation of the user_role parameter during user registration. This makes it possible for unauthenticated attackers to create accounts with elevated privileges, including administrator access.
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 Truelysell Core WordPress plugin fails to validate the user_role parameter during the registration process, allowing unauthenticated attackers to specify arbitrary roles including Administrator when creating new user accounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Truelysell Core plugin is installedNavigate to WordPress admin dashboard > Plugins and look for 'Truelysell Core' in the installed plugins listAffected if The plugin is present in the installation
-
Check installed Truelysell Core versionGo to Plugins > Installed Plugins > Truelysell Core and note the version number displayedAffected if Version is earlier than 1.8.8 (vulnerable); version 1.8.8 or later is patched
-
Confirm user registration is enabledGo to WordPress Settings > General > Membership and verify 'Anyone can register' is checked, then check if Truelysell Core registration form is active on the siteAffected if User registration is enabled and the Truelysell registration form is in use
-
Review administrator accounts for unauthorized accessGo to WordPress Users panel and examine all accounts with Administrator role. Check user registration dates and email addresses for any suspicious or recently created administrator accountsAffected if There are administrator accounts that were not created by existing site administrators or that appear suspicious
You are affected if the Truelysell Core plugin is installed with a version before 1.8.8 AND user registration is enabled on your WordPress site.
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.
dbcve · scopedUpdate Truelysell Core plugin to version 1.8.8 or later. As an interim measure, disable the user registration feature or restrict access to the registration endpoint via firewall rules.
Version greater than 1.8.7 (check WordPress plugin repository or ThemeForest for the latest release)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Truelysell Core plugin
- Check the current version number - if it is 1.8.7 or earlier, an update is needed
- If an update is available, click 'Update Now' to install the latest version
- After updating, verify the new version number in the plugins list
- Test user registration functionality to confirm the privilege escalation vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8572 — 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-2025-8572 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