Skip to main content
VulnerabilityPublished

CVE-2026-75833: getgrav grav · Open Redirect

Affects getgrav gravSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 1.0.14 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.14
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 15 Nov 2026.

What to do

Upgrade getgrav grav to 1.0.14.

Affected software

ProductAffectedFixed in
getgravgravAffected
  • <1.0.14
Fixed in
  • 1.0.14

AI-suggested

A fix is available in version 1.0.14 of the Grav API plugin. Users should upgrade to version 1.0.14 or later to remediate this open redirect vulnerability. Until then, avoid using untrusted input for returnTo parameters in OAuth flows.

Description

CVE-2026-75833 is an open redirect vulnerability in the Grav API plugin's SsoController::sanitizeReturnTo() function before version 1.0.14. The function attempts to block URLs with a '//' prefix but fails to handle browser normalization of backslashes to slashes, allowing crafted returnTo parameters like '/\evil.com' to redirect users to attacker-controlled sites after OAuth login. This can enable post-login phishing attacks. Exploitability depends on the client-side OAuth callback handler and was not independently verified.

References

Community reviews

Loading reviews…