Skip to content
Blog

vtenext · CRM

vtenext CVE-2025-71457: Change Any Account's Password Without Logging In

CVE-2025-71457 (VulnCheck CVSS 9.8): in vtenext 25.02, hub/rpwd.php changes any account's password with no token check. Fixed in vtenext 25.02.1.

4 min readCVE-2025-71457

CVE-2025-71457 was published by NVD on November 4, 2026. It affects vtenext 25.02, a self-hosted CRM, and it's disarmingly simple: the password recovery page lets anyone change the password of any account, with no token and no authentication, as long as they know a username.

If the targeted administrator hasn't enabled two-factor authentication, the attacker then logs in with the password they just picked.


The Vulnerability

FieldValue
CVECVE-2025-71457
CVSS 3.1 (VulnCheck)9.8 (CRITICAL) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 4.0 (VulnCheck)9.3 (CRITICAL)
TypeUnverified password change (CWE-620)
Authentication requiredNone
Affected versions25.02, before 25.02.1
NVD publication2026-11-04
NVD statusReceived (not yet analyzed)

NVD description (excerpt):

vtenext 25.02 before 25.02.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to change any account password via hub/rpwd.php without token verification.

The score comes from VulnCheck, which assigned the CVE. NVD hasn't analyzed it yet and publishes no CPE configuration.


How It Works

Password reset rests on one principle: users prove they control the account's email address by presenting a token they received by mail. That token is the only thing standing between "I'm asking for a reset" and "I'm changing the password".

In vtenext 25.02, according to NVD, that check is missing. The hub/rpwd.php script, with the action=change_password parameter, calls RecoverPwd::displayChangePwd() without verifying any token. All it takes is to:

  1. know a valid user_name (admin names are often guessable: admin, first.last…);
  2. send the password change request with a value of your choosing;
  3. log in with that password, if the account has no two-factor authentication.

NVD's mention of "administrators lacking two-factor authentication" draws the line clearly: the flaw changes anyone's password, but 2FA stops the attacker from turning it into a session.

One Link in a Longer Chain

The two research references cited by NVD (posts on 0xbro.red and on the Sicuranext blog) are titled "vtenext 25.02: a three-way path to RCE". The title indicates this flaw is part of paths leading to remote code execution; this CVE, as described by NVD, covers only the password change. Either way, a CRM admin account already opens up all customer data, contacts and sales history.


Affected and Fixed Versions

VersionStatus
vtenext 25.02affected
vtenext 25.02.1first version outside the range (NVD)

⚠️ That's the bound from the NVD description, not necessarily the version to install today. Check the vendor's release notes (usermanual.vtenext.com, 25.02.1 release note, cited by NVD) and install the latest version on your branch.

The NVD description says nothing about versions older than 25.02.


Detection

In web server logs:

  • requests to hub/rpwd.php containing action=change_password, especially with no prior reset request from the same client;
  • bursts of requests to that page with varying user_name values: a sign of someone probing for valid accounts.
grep -i "rpwd.php" /var/log/apache2/access.log* | grep -i "change_password"

In the application:

  • passwords changed without the user asking (a user who "can't log in anymore" is the first signal);
  • admin logins from unusual addresses;
  • recently added accounts, automation rules or modules.

Mitigation

1. Update to 25.02.1 or later

That's the fix. It doesn't undo passwords that were already changed.

2. Enable two-factor authentication on every admin account

The NVD description says it outright: admins without 2FA are the ones who can be taken over. It's the most effective measure, patched or not.

3. Until you update, block the page

Deny access to hub/rpwd.php at the reverse proxy or web server, at the cost of self-service password recovery for a few days. Better still: don't expose the CRM directly to the Internet, and put it behind a VPN or upstream authentication.

4. If you suspect exploitation

  1. Reset the passwords of all admin accounts
  2. Review created accounts, changed permissions and installed modules
  3. Treat CRM data, and the secrets it stores (mail connectors, third-party APIs), as exposed

Why Continuously Monitor Your Business Applications

A self-hosted CRM is rarely on the usual watch radar, which focuses on firewalls and operating systems. A 9.8 CVE with no NVD analysis and no CPE stays invisible to a product search for days, sometimes weeks.

With cveo.tech, add your business applications to your inventory with their exact versions, and get an alert as soon as a CVE affects them, even before NVD analysis.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.