Skip to main content
VulnerabilityPublished

CVE-2025-67165: pagekit · Insecure Direct Object Reference

Affects pagekitSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
GitHubpagekit/pagekitpkg:github/pagekit/pagekitOther 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. Monitor official Pagekit CMS channels for security advisories and apply patches immediately once available.
  2. Implement strict access control mechanisms at the application and web server levels to restrict unauthorized access to sensitive objects.
  3. Conduct thorough code reviews and penetration testing focused on authorization logic and object reference validation within the CMS.
  4. Employ Web Application Firewalls (WAFs) configured to detect and block suspicious requests that attempt to manipulate object references.
  5. Limit exposure of administrative interfaces to trusted IP addresses or VPNs to reduce attack surface.
  6. Enable detailed logging and continuous monitoring to detect anomalous activities indicative of exploitation attempts.
  7. Educate development and security teams about IDOR vulnerabilities and secure coding practices to prevent similar issues in custom extensions or integrations.
  8. Consider isolating the CMS environment in segmented network zones to contain potential breaches.

Description

An Insecure Direct Object Reference (IDOR) in Pagekit CMS v1.0.18 allows attackers to escalate privileges.

References

Community reviews

Loading reviews…