Pagekit CMS
CVE-2025-67165
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege Pagekit user
-
DeliverySend request with tampered object/role reference
-
ExploitBypass authorization check (IDOR)
-
ExecutionEscalate to administrator privileges
-
ImpactFull control over CMS content and users
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | The attacker must reach the Pagekit CMS application over the network and manipulate a user-controlled direct object reference (the user/role/permission identifier governing Pagekit's roles-and-permissions model documented in users.md#permissions and users.md#roles) to assign themselves elevated rights. Although the NVD vector states PR:N, the IDOR-to-privilege-escalation nature strongly implies a valid authenticated low-privilege session is required to issue the authorization-bypass request - this authentication prerequisite is the primary limiting factor and should be confirmed with the exploit POC. Exploitation is constrained to deployments running the specific vulnerable version Pagekit 1.0.18; the product is niche and largely unmaintained, further limiting real-world exposure. |
| Impact | The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) rates this 9.8 Critical, implying remote, unauthenticated, no-interaction exploitation with full C/I/A impact. However, this conflicts with the vulnerability class: an IDOR (CWE-639, Authorization Bypass Through User-Controlled Key) used to escalate privileges almost always requires an existing authenticated low-privilege account to manipulate a direct object reference (e.g., a user ID or role field) - verify PR with the vendor, as PR:N appears inconsistent with a privilege-escalation IDOR. The exploitation signals are mixed and point to lower real-world urgency than the 9.8 suggests: EPSS is only 0.50% (41st percentile), this CVE is NOT on the CISA KEV list (no confirmed active exploitation), and while public exploit code exists in a security researcher's GitHub repo, POC availability is distinct from active exploitation. Net assessment: a genuine, high-impact authorization flaw with a public POC, but mitigated by a niche affected product (Pagekit CMS), low EPSS, no KEV listing, and a likely authentication prerequisite - treat as a real but non-emergency priority, prioritizing patching only where Pagekit 1.0.18 is actually deployed. |
| Exploit ScenarioDerived | A registered low-privilege Pagekit user authenticates to the CMS and sends a request that references another object (such as a user/role identifier) they should not control, exploiting the IDOR to grant themselves administrator permissions. Publicly available exploit code exists in a GitHub research repository, lowering the skill required; because the CVSS vector lists AV:N/AC:L, the manipulation is performed over the network with low complexity once access to the application is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Privilege escalation in Pagekit CMS 1.0.18 via an insecure direct object reference (CWE-639) lets an attacker manipulate the user-, role-, or permission-identifier supplied in a request and assign themselves elevated rights within Pagekit's roles-and-permissions model. Publicly available exploit code exists (published in an mbiesiad vulnerability-research repository), but the flaw is not listed in CISA KEV and EPSS is only 0.50% (41st percentile), so no active exploitation has been confirmed. NVD scores it 9.8 with a PR:N vector, whereas the authoritative assessment requires a valid low-privilege authenticated session (PR:L); exploitation is confined to deployments running the specific, largely unmaintained 1.0.18 release, which limits real-world exposure.
RemediationAI
No vendor-released patch has been identified at time of analysis - none of the supplied references point to a fixed release, vendor advisory, or upstream commit, and Pagekit 1.0.18 appears effectively unmaintained, so upgrading to a patched 1.0.19+ build is not currently an option and should only be undertaken if the upstream project resumes releases. Until a fix exists, the highest-value compensating control is to treat every authenticated account as potentially dangerous: restrict who can hold even low-privilege accounts on the site, and reduce the role-assignment surface by removing or disabling any self-service profile, role-request, or user-management endpoint that accepts a client-supplied user/role/permission identifier (the trade-off is administrative overhead, since staff must manage roles out-of-band). Second, constrain network exposure - place Pagekit behind a reverse proxy or WAF rule that blocks untrusted networks from /admin, /user, and any role/permission-editing routes, and restrict CMS management interfaces to a VPN or allow-listed IP ranges; this meaningfully raises the bar for exploitation but complicates remote administration. Third, enable and monitor the CMS audit logs for unexpected role or permission changes, alerting on privilege grants made by low-privileged sessions (logging adds storage overhead and generates noise if not tuned). Fourth, given the project's inactivity and the availability of a public proof-of-concept (https://github.com/mbiesiad/vulnerability-research/tree/main/CVE-2025-67165), plan a migration to a maintained CMS if the risk cannot be accepted; running an unmaintained platform leaves any residual IDOR unfixed and should be documented as accepted risk if migration is deferred.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in composer
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), a class of IDOR in which the application trusts a client-supplied identifier - here the user, role, or permission record key used by Pagekit's roles-and-permissions subsystem - rather than verifying that the requesting session is authorized to modify that object. Pagekit's permission model, documented in the project's users.md#permissions and users.md#roles guides, maps users to roles and roles to granular permissions; because an attacker can substitute another object identifier, a low-privilege account can reach operations intended only for higher-privileged roles and thereby escalate privileges. The affected component is the Pagekit CMS application itself (CPE cpe:2.3:a:pagekit:pagekit:1.0.18), a PHP/MySQL content management system hosted at github.com/pagekit/pagekit. The assessment notes an important discrepancy: NVD's CVSS 3.1 vector reports AV:N/AC:L/PR:N/UI:N (unauthenticated), but the IDOR-to-privilege-escalation mechanics imply a valid low-privilege session is needed to issue the authorization-bypass request, so PR:L is used as the authoritative vector pending confirmation from the public proof-of-concept.
Know when Pagekit gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
IDOR privilege escalation (CWE-639) requires an authenticated low-privilege account to tamper with the object reference, so PR:L rather than PR:N; admin takeover yields full C/I/A impact.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
DescriptionCVE.org
An Insecure Direct Object Reference (IDOR) in Pagekit CMS v1.0.18 allows attackers to escalate privileges.
Executive ViewAI
Pagekit CMS 1.0.18 carries a critical access-control weakness that can let a low-privilege user grant themselves elevated permissions, potentially compromising site administration, content integrity, and any data managed by the platform. Organizations still running this specific, largely unmaintained release are affected, and leadership should care because publicly available exploit code exists while no vendor-released patch has been identified. Exposure is limited to 1.0.18 deployments and no confirmed active exploitation has been reported, but any internet-facing or high-value instance should be treated as a priority risk.
No vendor-released patch identified at time of analysis. Interim mitigations include inventorying and isolating Pagekit CMS 1.0.18 deployments, removing or blocking internet exposure, restricting access to trusted administrators and networks, enforcing least privilege, reviewing user/role/permission assignments, monitoring for unauthorized privilege changes, applying virtual patching or WAF rules if available, and migrating to a maintained CMS.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)CVE.org
Authenticated attackers with low privileges can upload a crafted PHP file to Pagekit CMS 1.0.18 via the /storage/poc.php
A file upload vulnerability exists in the storage feature of pagekit 1.0.18, which allows an attacker to upload maliciou
A CSRF vulnerability in Pagekit 1.0.17 allows an attacker to upload an arbitrary file by removing the CSRF token from a
Privilege escalation to remote code execution in Pagekit CMS 1.0.18 lets an authenticated user holding the 'user: manage
An issue was discovered in Pagekit CMS before 1.0.11. Rated high severity (CVSS 7.5), this vulnerability is remotely exp
An issue in Pagekit pagekit v.1.0.18 alows a remote attacker to execute arbitrary code via thedownloadAction and updateA
A cross-site scripting (XSS) vulnerability in Pagekit CMS v1.0.18 allows attackers to execute arbitrary web scripts or H
Pagekit before 1.0.14 has a /user/login?redirect= open redirect vulnerability. Rated medium severity (CVSS 6.1), this vu
In PageKit v1.0.18, a user can upload SVG files in the file upload portion of the CMS. Rated medium severity (CVSS 5.4),
The Reset Password feature in Pagekit 1.0.17 gives a different response depending on whether the e-mail address of a val
Stored XSS in YOOtheme Pagekit 1.0.13 and earlier allows a user to upload malicious code via the picture upload feature.
Pagekit 1.0.18 is vulnerable to Cross Site Scripting (XSS) in index.php/admin/site/widget. Rated medium severity (CVSS 4
NVD
CVE.org
EPSS
GitHub
Exploit-DB