The Search Analytics for WP plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4.16. This is due to missing or incorrect nonce validation on the process_bulk_action() function of MWTSA_Stats_Table. This makes it possible for unauthenticated attackers to delete arbitrary search-term records, including all associated search-history rows, via a forged request granted they can trick a user with access to the plugin's "Search Analytics" dashboard page (Administrator by default) into performing an action such as clicking on a link.
CVE-2026-7444
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 5, 2026
Last Modified
August 12, 2026
Advisory Details (1)
Auto-updated Aug 5, 2026Search Analytics for WP – WordPress plugin | WordPress.org
https://wordpress.org/plugins/search-analytics/Vendor Advisories for CVE-2026-7444(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 65× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 18:44 UTCGHSA enrichment
- 2026-08-20 06:54 UTCGHSA enrichment
- 2026-08-19 19:03 UTCEG score recompute
- 2026-08-19 19:03 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 07:12 UTCGHSA enrichment
- 2026-08-18 19:18 UTCGHSA enrichment
- 2026-08-18 07:27 UTCGHSA enrichment
- 2026-08-17 19:34 UTCEG score recompute
- 2026-08-17 19:34 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:43 UTCGHSA enrichment
- 2026-08-16 19:53 UTCEG score recompute
- 2026-08-16 19:53 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:02 UTCEG score recompute
- 2026-08-16 08:02 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 20:12 UTCGHSA enrichment
- 2026-08-15 08:21 UTCEG score recompute
- 2026-08-15 08:21 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 20:30 UTCGHSA enrichment
- 2026-08-14 08:40 UTCGHSA enrichment
Show 40 moreShow fewer
- 2026-08-13 20:49 UTCGHSA enrichment
- 2026-08-13 08:58 UTCGHSA enrichment
- 2026-08-12 21:07 UTCEG score recompute
- 2026-08-12 21:07 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 12:16 UTCGHSA enrichment
- 2026-08-12 00:25 UTCEG score recompute
- 2026-08-12 00:25 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 12:34 UTCGHSA enrichment
- 2026-08-11 00:44 UTCEG score recompute
- 2026-08-11 00:44 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 12:53 UTCGHSA enrichment
- 2026-08-10 01:02 UTCEG score recompute
- 2026-08-10 01:02 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 13:12 UTCGHSA enrichment
- 2026-08-09 01:22 UTCEG score recompute
- 2026-08-09 01:22 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 13:31 UTCGHSA enrichment
- 2026-08-08 01:40 UTCEG score recompute
- 2026-08-08 01:40 UTCGHSA enrichment
- 2026-08-07 13:49 UTCGHSA enrichment
- 2026-08-07 01:59 UTCGHSA enrichment
- 2026-08-06 14:09 UTCEG score recompute
- 2026-08-06 14:09 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 02:18 UTCEG score recompute
- 2026-08-06 02:18 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 14:27 UTCEG score recompute
- 2026-08-05 14:27 UTCGHSA enrichment
- 2026-08-05 13:47 UTCEG score recompute
- 2026-08-05 13:47 UTCGHSA enrichment
- 2026-08-05 08:23 UTCEG score recompute
- 2026-08-05 07:24 UTCEG score recompute
- 2026-08-05 07:20 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-7444?
When was CVE-2026-7444 disclosed?
Is CVE-2026-7444 actively exploited?
What is the CVSS score of CVE-2026-7444?
How do I remediate CVE-2026-7444?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-7444
Is Your Infrastructure Affected by CVE-2026-7444?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.