# CVE-2025-8572: Truelysell Core <= 1.8.7 - Unauthenticated Privilege Escalation via Registration

> Unauthenticated attackers can escalate privileges to administrator by manipulating the user_role parameter during registration in Truelysell Core.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-x6ph-vfh4-48q4

## What is CVE-2025-8572?

CVE-2025-8572 is a critical vulnerability in dreamstechnologies Truelysell Core, published on 14 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-8572?


## How do I fix CVE-2025-8572?

No fix has been published for CVE-2025-8572 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8572 being exploited?

There is no known exploitation of CVE-2025-8572 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8572 and fix it if it is affected.

What it is: CVE-2025-8572 is a critical vulnerability in dreamstechnologies Truelysell Core, published on 14 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8572 in the wild and no public exploit code.

Affected product: dreamstechnologies Truelysell Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8572/ (Markdown: https://insights.sbomify.com/CVE-2025-8572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8572
- OSV: https://osv.dev/vulnerability/CVE-2025-8572

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8572/
Summaries are generated and may contain mistakes; the official description above is the record.