CVE-2026-1667

HIGHPre-NVD 7.27.2
EchelonGraph scoreHIGH confidence

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-07-10. a secondary CVSS source baseline 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The SEO Plugin by Squirrly SEO plugin for WordPress is vulnerable to Arbitrary Post Creation and Stored Cross-Site Scripting in all versions up to, and including, 14.0.0 due to a leak of an API token and insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to create arbitrary posts, and, if the Advanced Custom Fields plugin is installed and activated, inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

CVSS v3
7.2
EG Score
7.2(high)
EG Risk
47(Track)
EG Risk 47/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 computed
Severity72% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Vendor Advisories for CVE-2026-1667(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 29× in last 7d / 69× 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.

  1. 2026-08-02 11:27 UTCEG score recompute
  2. 2026-08-02 11:27 UTCGHSA enrichment
  3. 2026-08-02 02:26 UTCEPSS rescore
  4. 2026-08-01 23:35 UTCGHSA enrichment
  5. 2026-08-01 11:42 UTCEG score recompute
  6. 2026-08-01 11:42 UTCGHSA enrichment
  7. 2026-08-01 04:15 UTCEPSS rescore
  8. 2026-07-31 23:50 UTCGHSA enrichment
  9. 2026-07-31 11:57 UTCGHSA enrichment
  10. 2026-07-31 00:03 UTCEG score recompute
  11. 2026-07-31 00:03 UTCGHSA enrichment
  12. 2026-07-30 12:10 UTCEG score recompute
  13. 2026-07-30 12:10 UTCGHSA enrichment
  14. 2026-07-30 01:30 UTCEPSS rescore
  15. 2026-07-30 00:06 UTCGHSA enrichment
  16. 2026-07-29 12:12 UTCGHSA enrichment
  17. 2026-07-29 00:20 UTCEG score recompute
  18. 2026-07-29 00:20 UTCGHSA enrichment
  19. 2026-07-28 12:25 UTCGHSA enrichment
  20. 2026-07-28 00:32 UTCEG score recompute
  21. 2026-07-28 00:32 UTCGHSA enrichment
  22. 2026-07-27 14:13 UTCEPSS rescore
  23. 2026-07-27 11:59 UTCGHSA enrichment
  24. 2026-07-27 00:06 UTCEG score recompute
  25. 2026-07-27 00:06 UTCGHSA enrichment
Show 44 more
  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 12:11 UTCEG score recompute
  4. 2026-07-26 12:10 UTCGHSA enrichment
  5. 2026-07-25 14:17 UTCEPSS rescore
  6. 2026-07-25 14:17 UTCEPSS rescore
  7. 2026-07-24 14:17 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:06 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 02:29 UTCEPSS rescore
  18. 2026-07-19 02:28 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-18 10:04 UTCEPSS rescore
  21. 2026-07-17 03:42 UTCGHSA enrichment
  22. 2026-07-16 17:03 UTCEPSS rescore
  23. 2026-07-16 17:03 UTCEPSS rescore
  24. 2026-07-16 15:50 UTCGHSA enrichment
  25. 2026-07-16 03:56 UTCGHSA enrichment
  26. 2026-07-15 16:57 UTCEPSS rescore
  27. 2026-07-15 16:57 UTCEPSS rescore
  28. 2026-07-15 16:04 UTCGHSA enrichment
  29. 2026-07-15 04:10 UTCGHSA enrichment
  30. 2026-07-15 02:00 UTCEPSS rescore
  31. 2026-07-15 02:00 UTCEPSS rescore
  32. 2026-07-14 16:14 UTCGHSA enrichment
  33. 2026-07-14 04:22 UTCGHSA enrichment
  34. 2026-07-13 22:30 UTCEPSS rescore
  35. 2026-07-13 16:28 UTCGHSA enrichment
  36. 2026-07-13 06:12 UTCEPSS rescore
  37. 2026-07-13 04:34 UTCGHSA enrichment
  38. 2026-07-12 16:42 UTCGHSA enrichment
  39. 2026-07-12 05:46 UTCEPSS rescore
  40. 2026-07-12 04:50 UTCGHSA enrichment
  41. 2026-07-11 16:57 UTCGHSA enrichment
  42. 2026-07-11 05:05 UTCGHSA enrichment
  43. 2026-07-10 17:13 UTCEG score recompute
  44. 2026-07-10 17:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-1667?
CVE-2026-1667 is a high vulnerability published on July 10, 2026. The SEO Plugin by Squirrly SEO plugin for WordPress is vulnerable to Arbitrary Post Creation and Stored Cross-Site Scripting in all versions up to, and including, 14.0.0 due to a leak of an API token and insufficient input sanitization and output escaping. This makes it possible for unauthenticated…
When was CVE-2026-1667 disclosed?
CVE-2026-1667 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1667 actively exploited?
CVE-2026-1667 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.5% of all scored CVEs.
What is the CVSS score of CVE-2026-1667?
CVE-2026-1667 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-1667?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1667, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-1667

Explore →

Is Your Infrastructure Affected by CVE-2026-1667?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.