VulnerabilityPublished 28 Dec 2025Updated 24 Feb 2026

CVE-2025-15153: PbootCMS · Files or Directories Accessible

Affects PbootCMSSource CVE Database V5

Public exploit available · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PbootCMS	Affected 3.2.0 – 3.2.12 13 affected builds	Fixed in–

AI-suggested

Immediately review and modify PbootCMS configuration settings to restrict access to the /data/pbootcms.db file, ensuring it is not accessible via the web server or unauthorized users.
Implement strict file system permissions on the database file and related directories to limit read/write access only to necessary system processes.
Monitor web server logs for unusual access patterns targeting the database file or related resources.
Deploy web application firewalls (WAF) with custom rules to detect and block attempts to access or manipulate the SQLite database file.
Regularly update PbootCMS to the latest version once patches addressing this vulnerability are released.
Conduct security audits and penetration testing focused on file access controls within the CMS environment.
Educate administrators on secure configuration practices specific to PbootCMS and SQLite database handling.
Isolate CMS environments in segmented network zones to limit lateral movement if exploitation occurs.

Description

A weakness has been identified in PbootCMS up to 3.2.12. Impacted is an unknown function of the file /data/pbootcms.db of the component SQLite Database. Executing a manipulation can lead to files or directories accessible. It is possible to launch the attack remotely. Attacks of this nature are highly complex. The exploitability is considered difficult. The exploit has been made available to the public and could be used for attacks. Modifying the configuration settings is advised.

Impact

The vulnerability allows remote attackers to access files or directories that should be protected, potentially exposing sensitive information such as configuration files, user data, or proprietary content. This unauthorized access can lead to data breaches, loss of confidentiality, and could facilitate further attacks such as privilege escalation or website defacement. Since PbootCMS is often used by small to medium-sized websites, the impact could range from reputational damage to compliance violations if sensitive data is leaked. The medium severity score reflects the balance between the potential impact and the difficulty of exploitation. However, the availability of public exploit code increases the risk that less skilled attackers might eventually exploit this vulnerability. Organizations worldwide relying on PbootCMS are at risk of data exposure and should consider this vulnerability a significant security concern.

Summary

CVE-2025-15153 is a vulnerability identified in PbootCMS, a content management system widely used for website management, affecting all versions up to 3.2.12. The issue arises from improper access controls related to the SQLite database file located at /data/pbootcms.db. An attacker can remotely manipulate this file to gain unauthorized access to files or directories within the system. The vulnerability does not require authentication or user interaction, but the attack complexity is high, indicating that exploitation demands advanced skills or specific conditions. The impact is primarily on confidentiality, as unauthorized file access could expose sensitive data stored within the CMS environment. The vulnerability has a CVSS 4.0 base score of 6.3, reflecting medium severity, with network attack vector, high attack complexity, and no privileges or user interaction needed. Although no active exploitation has been reported in the wild, public exploit code is available, increasing the risk of future attacks. Mitigation recommendations include modifying configuration settings to restrict access to the database file and applying any available patches once released. Organizations using PbootCMS should audit their systems to identify vulnerable versions and implement protective measures promptly.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:33 UTC

Technical details

References

Community reviews

Related threats