CVE-2026-79387: SQL Injection

Q: What level of access does an attacker need to exploit this issue?

The attacker must be authenticated to the PbootCMS application. The provided information does not indicate that unauthenticated users can exploit it.

Q: What could an attacker change if exploitation succeeds?

An authenticated attacker can modify arbitrary user account fields through crafted parameters to the User/mod interface. This includes passwords and roles, which can enable takeover of other accounts or privilege escalation.

Q: Which deployments are known to be affected?

PbootCMS versions 3.2.0 through 3.2.5 are identified as affected.

Published Sep 9, 2026

Updated

SQL injection vulnerability in PbootCMS versions 3.2.0 through 3.2.5 allows an authenticated user to modify arbitrary user account fields (including passwords and roles) via crafted parameters to the User/mod interface, enabling account takeover.

Affected Software

1 affected component

Pbootcms Pbootcms>=3.2.0<=3.2.5

Event History

Sep 9, 2026

CVE Published

via NVD·09:17 PM

Data Sourced

via NVD·09:17 PM

Description

Frequently Asked Questions

What level of access does an attacker need to exploit this issue?

The attacker must be authenticated to the PbootCMS application. The provided information does not indicate that unauthenticated users can exploit it.

What could an attacker change if exploitation succeeds?

An authenticated attacker can modify arbitrary user account fields through crafted parameters to the User/mod interface. This includes passwords and roles, which can enable takeover of other accounts or privilege escalation.

Which deployments are known to be affected?

PbootCMS versions 3.2.0 through 3.2.5 are identified as affected.

CVE-2026-79387: SQL Injection

Affected Software

Event History

Frequently Asked Questions

What level of access does an attacker need to exploit this issue?

What could an attacker change if exploitation succeeds?

Which deployments are known to be affected?

Company

Resources

Contact

Frequently Asked Questions

What level of access does an attacker need to exploit this issue?

What could an attacker change if exploitation succeeds?

Which deployments are known to be affected?