External risk intelligence

Pagekit CMS Arbitrary File Upload Vulnerability Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2025-67164

Pagekit is a content management system designed for web hosting. As a CMS, it is commonly deployed as a public-facing web application. The vulnerability exists within an application component that is reachable via the web interface, making internet exposure for this type of product a standard deployment pattern.

OS Command Injection

Pagekit

1.0.18

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability affects Pagekit CMS, a web content management system, specifically in its file storage component. It allows authenticated users to upload malicious files, potentially leading to the execution of arbitrary code on the system. The main concern is confirming relevance and exposure to this type of content management system.

  • Authenticated users can upload malicious code.
  • It allows attackers to run unauthorized code.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with existing access to the Pagekit CMS can exploit a vulnerability in the `/storage/poc.php` component by uploading a specially crafted PHP file. This could allow them to execute arbitrary code on the server.

  • Requires authenticated access.
  • Uploading a crafted PHP file.
  • Arbitrary code execution on the server.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated attacker to upload and execute arbitrary code on the server when supported by the advisory's context. This could affect the integrity and availability of the system.

  • Server-side code execution is at risk.
  • Arbitrary file upload via a PHP component.
  • Complete server compromise is possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects authenticated users of Pagekit CMS. The first step is to identify all instances of Pagekit CMS within your environment, determine their reachability and business criticality, and locate the accountable owner for each instance to prioritize remediation efforts.

  • Identify Pagekit CMS instances and owners.
  • Verify external reachability and business impact.
  • Plan risk-based remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Pagekit CMS?

Pagekit is a modular, open-source content management system built with PHP and the Vue.js framework. It provides administrators with a web-based interface to manage website content, themes, and extensions. Because it acts as a central hub for web publishing, it is typically hosted on servers where it processes user input and manages file storage for site assets.

How does CVE-2025-67164 work?

This vulnerability is classified as an Unrestricted Upload of File with Dangerous Type (CWE-434), which often leads to Code Injection (CWE-94) and OS Command Injection (CWE-78). In this specific case, the software fails to properly validate files sent to the /storage/poc.php component. An attacker can upload a malicious PHP script disguised as a valid file, which the server then executes, granting the attacker the ability to run commands on the underlying system.

Do I need special access to trigger this bug?

Yes. The vulnerability requires the attacker to be authenticated as a user within the Pagekit CMS environment. It cannot be triggered by an unauthenticated visitor or an anonymous user attempting to access the site. The security gap specifically exists in the file handling logic provided to users who have already gained access to the application's internal functions.

Is my Pagekit instance at risk?

According to Halo Surface Signal, because Pagekit is a content management system, it is frequently deployed as a public-facing web application. Any instance reachable over the internet is a higher priority concern. If your Pagekit installation is accessible to the public, an attacker who obtains valid user credentials could reach the vulnerable file upload component remotely.

Why should I audit my Pagekit installations now?

Since this flaw allows for full server-side code execution, it poses a severe risk to your site's integrity. You should start by creating an inventory of all Pagekit CMS deployments in your environment. Confirm which instances are exposed to the internet, identify the business owners responsible for those sites, and ensure you are prepared to apply updates or restrict access to the storage component once a patch is provided.

References