CVE-2026-61457

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory published 2026-07-15. a secondary CVSS source baseline 8.8; sources differ by 0.0.

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

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

The Grav API plugin (getgrav/grav-plugin-api) before 1.0.3 contains a file upload extension bypass in the API media controller. HandlesMediaUploads::validateFileExtension() inspects only the final file extension via pathinfo($filename, PATHINFO_EXTENSION), so a user with api.media.write permission can upload a file with a double extension such as shell.php.jpg to bypass the dangerous extensions blocklist. The web server may then execute the file as PHP, resulting in remote code execution.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
—
KEV
Not listed

Published

July 15, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jul 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Grav before 1.0.3 Remote Code Execution via File Upload Extension Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/grav-before-remote-code-execution-via-file-upload-extension-bypass
github Patch Available🟡 PoC Available

File Upload Extension Bypass in API Media Controller · Advisory · getgrav/grav · GitHub

https://github.com/getgrav/grav/security/advisories/GHSA-66v2-vxxf-xc3v

Vendor Advisories for CVE-2026-61457(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 4× in last 7d / 4× 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-07-16 00:56 UTCEG score recompute
  2. 2026-07-16 00:56 UTCGHSA enrichment
  3. 2026-07-15 11:54 UTCEG score recompute
  4. 2026-07-15 11:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-61457?
CVE-2026-61457 is a high vulnerability published on July 15, 2026. The Grav API plugin (getgrav/grav-plugin-api) before 1.0.3 contains a file upload extension bypass in the API media controller. HandlesMediaUploads::validateFileExtension() inspects only the final file extension via pathinfo($filename, PATHINFO_EXTENSION), so a user with api.media.write permission…
When was CVE-2026-61457 disclosed?
CVE-2026-61457 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-61457?
CVE-2026-61457 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-61457?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61457, 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-61457

Explore →

Is Your Infrastructure Affected by CVE-2026-61457?

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

Start Free Scan →Browse All CVEs