# CVE-2025-10742: Truelysell Core <= 1.8.6 - Unauthenticated Arbitrary User Password Change

> Unauthenticated attackers can change user passwords and take over administrator accounts if they know the specific page containing the vulnerable shortcode.

- **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:** 16 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-x7x8-rfpp-v489

## What is CVE-2025-10742?

CVE-2025-10742 is a critical authentication bypass vulnerability in dreamstechnologies Truelysell Core, published on 16 Oct 2025. 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 Arbitrary User Password Change in versions up to, and including, 1.8.6. This is due to the plugin providing user-controlled access to objects, letting a user bypass authorization and access system resources. This makes it possible for unauthenticated attackers to change user passwords and potentially take over administrator accounts. Note: This can only be exploited unauthenticated if the attacker knows which page contains the 'truelysell_edit_staff' shortcode.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-10742 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10742 is a critical authentication bypass vulnerability in dreamstechnologies Truelysell Core, published on 16 Oct 2025. 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-10742 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-10742/ (Markdown: https://insights.sbomify.com/CVE-2025-10742/index.md)
```

## Sources

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

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