VulnerabilityPublished 21 Mar 2026Updated 23 Mar 2026

CVE-2026-4510: PbootCMS · Cross-site Scripting

Affects PbootCMSSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 4.0 base score

5.3Medium

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
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: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to 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 21 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 1 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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–
GitHubzzj-create/pbootcms`pkg:github/zzj-create/pbootcms`Other threats	Affected 3.2.0 – 3.2.12 13 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:pbootcms:pbootcms:*:*:*:*:*:*:*:*

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

AI-suggested

Upgrade PbootCMS to a version newer than 3.2.12 once an official patch addressing CVE-2026-4510 is released.
In the interim, implement strict input validation and output encoding on the 'backurl' parameter within the alert_location function to neutralize malicious script injections.
Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting the 'backurl' parameter.
Educate users and administrators about the risks of clicking untrusted links and implement anti-phishing measures such as email filtering and URL scanning.
Review and harden Content Security Policy (CSP) headers to restrict script execution sources, mitigating the impact of XSS attacks.
Conduct regular security audits and penetration testing focused on input handling and parameter sanitization.
Monitor web server logs for unusual requests containing suspicious 'backurl' parameter values to detect attempted exploitation.
Disable or restrict the use of the alert_location function if feasible until a patch is applied.

Description

A weakness has been identified in PbootCMS up to 3.2.12. This impacts the function alert_location of the file apps/home/controller/MemberController.php of the component Parameter Handler. This manipulation of the argument backurl causes cross site scripting. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks.

Impact

The primary impact of CVE-2026-4510 is the potential for attackers to execute arbitrary scripts in users' browsers, leading to session hijacking, theft of sensitive information such as cookies or credentials, and phishing attacks through malicious redirection. This can undermine user trust and compromise user accounts on affected websites. For organizations, this could result in data breaches, unauthorized access, reputational damage, and potential regulatory penalties if user data is exposed. Since the vulnerability is remotely exploitable without authentication, any public-facing PbootCMS instance running vulnerable versions is at risk. The requirement for user interaction limits automated exploitation but does not eliminate risk, especially in targeted phishing campaigns. The absence of known active exploits currently reduces immediate threat but the public availability of exploit code increases the likelihood of future attacks. Organizations relying on PbootCMS for critical web services, especially those handling sensitive user data, face moderate risk until remediation is applied.

References

Community reviews

Loading reviews…