dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-7052

HIGH · 8.8 CVSS v3.1 Published 2025-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 LatePoint plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.1.94. This is due to missing nonce validation on the change_password() function of its customer_cabinet__change_password AJAX route. The plugin hooks this endpoint via wp_ajax and wp_ajax_nopriv but does not verify a nonce or user capability before resetting the user’s password. This makes it possible for unauthenticated attackers who trick a logged-in customer (or, with “WP users as customers” enabled, an administrator) into visiting a malicious link to take over their account.

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 LatePoint WordPress plugin lacks nonce validation on its customer_cabinet__change_password AJAX endpoint, which is accessible to unauthenticated users via wp_ajax and wp_ajax_nopriv hooks. Attackers can craft malicious links that, when clicked by a logged-in customer or administrator (with WP users as customers enabled), will reset the victim's password to a value of the attacker's choosing, enabling full account takeover.

MitigationUpgrade to LatePoint version 5.1.95 or later, which adds proper nonce validation and capability checks to the password change endpoint. Until then, advise users to avoid clicking untrusted links while logged in.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm LatePoint plugin is installed
    Check the WordPress plugins directory or navigate to Plugins > Installed Plugins in the WP admin dashboard to verify the LatePoint plugin is present and active
    Affected if LatePoint plugin is installed and active on the WordPress site
  2. Identify installed LatePoint version
    In WP admin, go to Plugins > Installed Plugins and look for the LatePoint plugin version number, or check the main plugin file header for the Version field
    Affected if Version is lower than 5.1.95 (vulnerable); version 5.1.95 or later includes the fix
  3. Verify WP users as customers setting
    Navigate to LatePoint > Settings > Customers (or similar settings area) and check if the option to use WordPress users as customers is enabled
    Affected if This setting is enabled - the vulnerability requires WP users to be used as customers for the attack to succeed
  4. Check AJAX endpoint accessibility
    Inspect the LatePoint plugin files (typically in wp-content/plugins/latepoint) for the registration of wp_ajax_nopriv_customer_cabinet__change_password or wp_ajax_customer_cabinet__change_password hooks without nonce validation
    Affected if The AJAX action customer_cabinet__change_password is registered with wp_ajax_nopriv and lacks nonce verification in the callback function

The site is affected if LatePoint version is below 5.1.95 AND the WP users as customers setting is enabled, allowing unauthenticated password reset requests to succeed when clicked by a logged-in user.

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

Upgrade to LatePoint version 5.1.95 or later, which adds proper nonce validation and capability checks to the password change endpoint. Until then, advise users to avoid clicking untrusted links while logged in.

Recommended fix High confidence

LatePoint version 5.1.95 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the LatePoint plugin in the list
  4. Click 'Update now' if an update is available, or manually update to version 5.1.95 or later
  5. After updating, verify the plugin version shows 5.1.95 or higher under the plugin name
  6. Test that the password change functionality still works correctly in the customer cabinet
Caveat No known breaking changes for this security update; this is a nonce validation fix

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-7052 — 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-7052 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