Skip to main content
CVE-2025-50286VulnerabilityPublished Updated

CVE-2025-50286: n/a

Source CVE Database V5

0

Not known to be exploited · public exploit available (Metasploit, Exploit-DB) · 13% EPSS · CVSS 8.1 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
13.6% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 6 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

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

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by mitre

    , 51 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , the same day as disclosure

  4. First Exploit-DB entry (opens in a new tab)

    Grav CMS 1.7.48 - Remote Code Execution (RCE)

    , 5 days after disclosure

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 2026-10-26.

What to do

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Immediately restrict access to the Grav CMS admin interface using network-level controls such as VPNs, IP whitelisting, or multi-factor authentication (MFA) to reduce the risk of unauthorized admin access. 2) Enforce strong password policies and implement MFA for all admin accounts to prevent credential compromise. 3) Monitor and audit admin activities and plugin uploads for suspicious behavior or unauthorized changes. 4) Disable or restrict the /admin/tools/direct-install interface if plugin installation is not frequently required, or replace it with a manual plugin installation process that includes integrity verification. 5) Apply any available patches or updates from Grav CMS as soon as they are released. 6) Conduct regular security assessments and penetration testing focused on CMS components. 7) Implement web application firewalls (WAFs) with rules to detect and block malicious payloads or unusual plugin upload patterns. 8) Educate administrators on phishing and social engineering risks to protect admin credentials. These measures go beyond generic advice by focusing on reducing the likelihood of admin credential compromise and limiting the attack surface of the vulnerable interface.

Description

A Remote Code Execution (RCE) vulnerability in Grav CMS v1.7.48 allows an authenticated admin to upload a malicious plugin via the /admin/tools/direct-install interface. Once uploaded, the plugin is automatically extracted and loaded, allowing arbitrary PHP code execution and reverse shell access.

References

Community reviews

Loading reviews…