Skip to main content
CVE-2025-67164VulnerabilityPublished

CVE-2025-67164: vulnerability-research · n/a

Affects vulnerability-researchSource CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 08:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 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

Affected software

ProductAffectedFixed in
GitHubmbiesiad/vulnerability-researchpkg:github/mbiesiad/vulnerability-researchOther threatsAffected
  • =1.0.18
Fixed in–

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

AI-suggested

1. Immediate Actions: Restrict access to the /storage/poc.php endpoint to trusted administrators only, using IP whitelisting or network segmentation. 2. Authentication Hardening: Enforce strong authentication mechanisms and monitor for suspicious login attempts to reduce the risk of credential compromise. 3. Input Validation: Implement strict server-side validation to restrict file types and sanitize file names during upload processes. 4. File Upload Controls: Disable or limit file upload functionality where not necessary, and enforce storage of uploaded files outside the web root to prevent direct execution. 5. Web Application Firewall (WAF): Deploy and configure a WAF with rules to detect and block malicious file uploads and suspicious HTTP requests targeting the vulnerable component. 6. Monitoring and Logging: Enhance logging around file upload activities and monitor for anomalous behavior indicative of exploitation attempts. 7. Patch Management: Monitor Pagekit CMS vendor communications for official patches or updates addressing this vulnerability and apply them promptly once available. 8. Incident Response Preparedness: Prepare to respond to potential incidents by having backups and recovery plans in place for affected web servers. These steps go beyond generic advice by focusing on immediate access restrictions, enhanced monitoring, and architectural controls to mitigate risk until a patch is released.

Description

An authenticated arbitrary file upload vulnerability in the /storage/poc.php component of Pagekit CMS v1.0.18 allows attackers to execute arbitrary code via uploading a crafted PHP file.

References

Community reviews

Loading reviews…