CVE-2026-16585

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
7.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 7.2Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Wordfence) lists wordplus Better Messages – Chat Rooms, Group Chat, Private Messages & AI Chat Bots versions up to and including 2.15.19 as affected. No release containing a fix is confirmed on record.

The Better Messages – Chat Rooms, Group Chat, Private Messages & AI Chat Bots plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_sticker function in all versions up to, and including, 2.15.19. This makes it possible for authenticated attackers, with administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The prefix check intended to restrict deletion to the uploads directory can be bypassed by crafting a URL that begins with the legitimate uploads base URL but embeds ../ traversal sequences in the path portion, as the normalize_sticker function only applies esc_url_raw(), which does not strip ../ sequences, allowing the traversal payload to be stored verbatim in WordPress options.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
33
EG Risk 33/100

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 (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
1.2%
EPSS %ILE
66th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 28, 2026

Last Modified

July 28, 2026

References (6)

Vendor Advisories for CVE-2026-16585(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 12× in last 7d / 59× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  4. 2026-10-12 16:30 UTCEG score recompute
  5. 2026-10-11 20:09 UTCEG score recompute
  6. 2026-10-11 17:21 UTCEG score recompute
  7. 2026-10-11 14:54 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  13. 2026-10-07 00:08 UTCEG score recompute
  14. 2026-10-07 00:08 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  17. 2026-10-04 23:21 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  18. 2026-10-04 07:12 UTCEG score recompute
  19. 2026-10-04 07:12 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  20. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  21. 2026-10-02 18:25 UTCEG score recompute
  22. 2026-10-02 18:25 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  23. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  24. 2026-10-01 16:13 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  25. 2026-10-01 03:45 UTCEG score recompute
Show 75 more
  1. 2026-10-01 03:45 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  2. 2026-09-30 15:02 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  3. 2026-09-29 15:20 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  4. 2026-09-29 07:48 UTCEG score recompute
  5. 2026-09-29 07:48 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  6. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  7. 2026-09-28 03:27 UTCEG score recompute
  8. 2026-09-28 03:27 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  9. 2026-09-27 13:47 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  10. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  11. 2026-09-25 06:25 UTCEG score recompute
  12. 2026-09-25 06:25 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  13. 2026-09-24 11:05 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  14. 2026-09-23 22:38 UTCEG score recompute
  15. 2026-09-23 22:38 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  16. 2026-09-23 10:11 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  17. 2026-09-22 21:44 UTCEG score recompute
  18. 2026-09-22 21:44 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  19. 2026-09-20 00:38 UTCEG score recompute
  20. 2026-09-20 00:38 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  21. 2026-09-19 08:07 UTCEG score recompute
  22. 2026-09-19 08:07 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  23. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-09-18 17:57 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  25. 2026-09-18 02:10 UTCEG score recompute
  26. 2026-09-18 02:10 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  27. 2026-09-17 01:42 UTCEG score recompute
  28. 2026-09-17 01:42 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  29. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  30. 2026-09-16 05:55 UTCEG score recompute
  31. 2026-09-16 05:55 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  32. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-09-15 08:53 UTCEG score recompute
  34. 2026-09-15 08:53 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  35. 2026-09-14 15:31 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  36. 2026-09-14 01:07 UTCEG score recompute
  37. 2026-09-14 01:07 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  38. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  39. 2026-09-13 12:35 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  40. 2026-09-13 00:04 UTCEG score recompute
  41. 2026-09-13 00:04 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  42. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  43. 2026-09-12 09:58 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  44. 2026-09-11 21:30 UTCEG score recompute
  45. 2026-09-11 21:30 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  46. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  47. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  48. 2026-09-11 09:02 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  49. 2026-09-10 20:34 UTCEG score recompute
  50. 2026-09-10 20:34 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  51. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  52. 2026-09-10 07:50 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  53. 2026-09-09 08:07 UTCEG score recompute
  54. 2026-09-09 08:07 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  55. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  56. 2026-09-07 20:57 UTCEG score recompute
  57. 2026-09-07 20:57 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  58. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  59. 2026-09-06 23:18 UTCEG score recompute
  60. 2026-09-06 23:17 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  61. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  62. 2026-09-06 07:38 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  63. 2026-09-05 19:11 UTCEG score recompute
  64. 2026-09-05 19:11 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  65. 2026-09-05 05:34 UTCEG score recompute
  66. 2026-09-05 05:34 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  67. 2026-09-04 12:09 UTCEG score recompute
  68. 2026-09-04 12:08 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  69. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  70. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  71. 2026-09-01 22:55 UTCEG score recompute
  72. 2026-09-01 22:55 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2
  73. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  74. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  75. 2026-09-01 00:51 UTCGHSA enrichmentGHSA-6fr4-j24c-qcq7 · GitHub severity HIGH · GitHub CVSS 7.2

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16585?
CVE-2026-16585 is a high-severity vulnerability; its CVE record was published on July 28, 2026. The Better Messages – Chat Rooms, Group Chat, Private Messages & AI Chat Bots plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the deletesticker function in all versions up to, and including, 2.15.19. This makes it possible for authenticated…
When was the CVE record for CVE-2026-16585 published?
The CVE record for CVE-2026-16585 was published on July 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 28, 2026; the record at its source may have been updated since.
Is CVE-2026-16585 actively exploited?
CVE-2026-16585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16585?
CVE-2026-16585 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16585?
No fix for CVE-2026-16585 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Wordfence) lists wordplus Better Messages – Chat Rooms, Group Chat, Private Messages & AI Chat Bots versions up to and including 2.15.19 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-16585 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16585?

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

Book a Demo →Browse All CVEs