CVE-2025-6754 json
SEO Metrics <= 1.0.15 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation
published 2025-08-02 15 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-23426
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
The SEO Metrics plugin for WordPress is vulnerable to Privilege Escalation due to missing authorization checks in both the seo_metrics_handle_connect_button_click() AJAX handler and the seo_metrics_handle_custom_endpoint() function in all versions up to, and including, 1.0.15. Because the AJAX action only verifies a nonce, without checking the caller’s capabilities, a subscriber-level user can retrieve the token and then access the custom endpoint to obtain full administrator cookies.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 15 mo ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- seometricsplugin SEO Metrics
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/48658b33-ae53-4919-8180-1188f72553f7?source=cve
- wordpress.org /plugins/seo-metrics-helper/#developers
- plugins.trac.wordpress.org /browser/seo-metrics-helper/trunk/endpoint.php
- plugins.trac.wordpress.org /browser/seo-metrics-helper/trunk/common-functions.php
- plugins.trac.wordpress.org /browser/seo-metrics-helper/trunk/seo-metrics.php
- plugins.trac.wordpress.org /browser/seo-metrics-helper/trunk/welcome-page.php
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3343566%40seo-metrics-helper&new=3343566%40seo-metrics-helper
Sources
- CVE List CVE-2025-6754
- NVD CVE-2025-6754
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.