CVE-2026-16263

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

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

The WP Maps WordPress plugin before 4.9.7 does not perform a capability check in one of its AJAX actions and does not properly validate a user-controlled path before using it in a file inclusion, allowing users with a Subscriber account to include and execute arbitrary existing local PHP files on the server.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

WP Maps < 4.9.7 – Subscriber+ Local File Inclusion | CVE 2026-16263 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/015d7f26-81f2-4b15-b52e-3d28d68eb5bd/

Vendor Advisories for CVE-2026-16263(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 / 58× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 20:36 UTCGHSA enrichment
  3. 2026-08-20 07:41 UTCGHSA enrichment
  4. 2026-08-19 18:47 UTCEG score recompute
  5. 2026-08-19 18:47 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 04:35 UTCGHSA enrichment
  8. 2026-08-18 15:40 UTCEG score recompute
  9. 2026-08-18 15:40 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 00:57 UTCEG score recompute
  12. 2026-08-18 00:57 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 12:02 UTCGHSA enrichment
  15. 2026-08-16 23:07 UTCEG score recompute
  16. 2026-08-16 23:07 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 10:12 UTCEG score recompute
  19. 2026-08-16 10:12 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 21:18 UTCGHSA enrichment
  22. 2026-08-15 08:23 UTCEG score recompute
  23. 2026-08-15 08:23 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 19:28 UTCGHSA enrichment
Show 33 more
  1. 2026-08-14 06:34 UTCEG score recompute
  2. 2026-08-14 06:34 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 17:39 UTCGHSA enrichment
  5. 2026-08-13 04:37 UTCGHSA enrichment
  6. 2026-08-12 15:43 UTCEG score recompute
  7. 2026-08-12 15:43 UTCGHSA enrichment
  8. 2026-08-12 13:50 UTCEPSS rescore
  9. 2026-08-12 02:48 UTCGHSA enrichment
  10. 2026-08-11 13:54 UTCEG score recompute
  11. 2026-08-11 13:54 UTCGHSA enrichment
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-11 00:59 UTCEG score recompute
  14. 2026-08-11 00:59 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 12:04 UTCGHSA enrichment
  17. 2026-08-09 23:07 UTCEG score recompute
  18. 2026-08-09 23:07 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 10:12 UTCGHSA enrichment
  21. 2026-08-08 21:18 UTCEG score recompute
  22. 2026-08-08 21:18 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 08:23 UTCEG score recompute
  25. 2026-08-08 08:23 UTCGHSA enrichment
  26. 2026-08-07 19:29 UTCEG score recompute
  27. 2026-08-07 19:29 UTCGHSA enrichment
  28. 2026-08-07 18:29 UTCEG score recompute▲ 8.80
  29. 2026-08-07 18:29 UTCGHSA enrichment
  30. 2026-08-07 18:28 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  31. 2026-08-07 06:20 UTCNVD update
  32. 2026-08-07 06:03 UTCEG score recompute
  33. 2026-08-07 06:03 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16263?
CVE-2026-16263 is a high vulnerability published on August 7, 2026. The WP Maps WordPress plugin before 4.9.7 does not perform a capability check in one of its AJAX actions and does not properly validate a user-controlled path before using it in a file inclusion, allowing users with a Subscriber account to include and execute arbitrary existing local PHP files on…
When was CVE-2026-16263 disclosed?
CVE-2026-16263 was first published in the National Vulnerability Database on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16263 actively exploited?
CVE-2026-16263 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 73.3% of all scored CVEs.
What is the CVSS score of CVE-2026-16263?
CVE-2026-16263 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16263?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16263, 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-16263

Explore →

Is Your Infrastructure Affected by CVE-2026-16263?

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

Start Free Scan →Browse All CVEs