Skip to main content
VulnerabilityPublished Updated

CVE-2025-66844: grav · Server-Side Request Forgery (SSRF)

Affects gravSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.7.49.5 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.49.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade yohane-mashiro/grav to 1.7.49.5.

Affected software

ProductAffectedFixed in
GitHubyohane-mashiro/gravpkg:github/yohane-mashiro/gravOther threatsAffected
  • <1.7.49.5
Fixed in
  • 1.7.49.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade Grav CMS installations to version 1.7.49.5 or later where the vulnerability is patched.
  2. Audit and harden Twig template configurations to disallow registration or invocation of undefined PHP functions, preventing SSRF vectors.
  3. Implement strict input validation and sanitization on any user-controllable content processed by Twig templates.
  4. Employ network segmentation and firewall rules to restrict outbound HTTP requests from web servers to only necessary destinations, limiting SSRF impact.
  5. Monitor web server logs and network traffic for unusual outbound requests indicative of SSRF exploitation attempts.
  6. Use Web Application Firewalls (WAFs) with rules designed to detect and block SSRF attack patterns targeting Grav CMS.
  7. Conduct regular security assessments and code reviews focusing on template processing and server-side request handling.
  8. Educate development and operations teams about secure template usage and configuration best practices to prevent similar vulnerabilities.

Description

In grav <1.7.49.5, a SSRF (Server-Side Request Forgery) vector may be triggered via Twig templates when page content is processed by Twig and the configuration allows undefined PHP functions to be registered

References

Community reviews

Loading reviews…