dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-10742

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

The Truelysell Core WordPress plugin versions up to 1.8.6 contains an Insecure Direct Object Reference (IDOR) vulnerability in the truelysell_edit_staff shortcode functionality. This allows unauthenticated attackers to bypass authorization checks and change arbitrary user passwords by manipulating user IDs in the request. The vulnerability can be exploited without authentication if attackers identify a page containing the vulnerable shortcode.

MitigationUpdate the Truelysell Core plugin to the latest patched version immediately. Until patched, restrict access to pages containing the truelysell_edit_staff shortcode or disable the plugin entirely if the functionality is not critical.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Truelysell Core plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find Truelysell Core. Check the version number in the plugin description, or inspect the file wp-content/plugins/truelysell-core/truelysell-core.php and look for the Version header in the plugin comment block.
    Affected if The installed version is 1.8.6 or any earlier version (e.g., 1.8.5, 1.8.0, etc.)
  2. Search for the vulnerable shortcode in content
    Search your WordPress database for pages or posts containing the shortcode 'truelysell_edit_staff'. You can do this via phpMyAdmin by querying wp_posts where post_content LIKE '%truelysell_edit_staff%' and post_status = 'publish', or use a plugin like Search Regex to search for this string.
    Affected if Any published page, post, or custom post type contains the [truelysell_edit_staff] shortcode
  3. Test unauthenticated access to the shortcode page
    Log out of WordPress completely, then visit the URL of a page where the truelysell_edit_staff shortcode is present. Observe whether the page loads fully (HTTP 200) or redirects you to a login page.
    Affected if The page loads and displays content without requiring authentication (you are not redirected to wp-login.php)
  4. Inspect for password change exposure
    On the shortcode page accessed without authentication, look for any user edit form, password reset fields, or staff management interface. Check the page source (View > Page Source) for form elements related to password changes or user updates.
    Affected if Password change fields, user edit forms, or staff management interfaces are visible to unauthenticated visitors

You are affected if Truelysell Core plugin version is 1.8.6 or lower AND any published page contains the [truelysell_edit_staff] shortcode that is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Truelysell Core plugin to the latest patched version immediately. Until patched, restrict access to pages containing the truelysell_edit_staff shortcode or disable the plugin entirely if the functionality is not critical.

Recommended fix Moderate confidence

Version greater than 1.8.6 (contact the plugin developer or check ThemeForest for the latest fixed release)

  1. 1. Check the current version of the Truelysell Core plugin installed on your WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. If a newer version of Truelysell Core is available, click 'Update Now' to install the latest version
  4. 4. After updating, verify that the version is greater than 1.8.6
  5. 5. Test the 'truelysell_edit_staff' functionality to ensure it still works properly after the update
  6. 6. Consider changing passwords for administrator accounts as a precautionary measure
Caveat Minor - the update addresses a security vulnerability; verify normal functionality after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10742 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10742 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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