Is CVE-2026-57995 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57995 being exploited in the wild.

How severe is CVE-2026-57995?

High severity, with a CVSS score of 8.8, published 30 June 2026.

Which products and versions are affected?

phpmyfaq/phpmyfaq (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.5; thorsten/phpmyfaq (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.5.

Is there a fix for CVE-2026-57995?

Yes. phpmyfaq/phpmyfaq (Packagist): upgrade to 4.1.5 or later; thorsten/phpmyfaq (Packagist): upgrade to 4.1.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-57995 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-57995?

Check whether you run phpmyfaq/phpmyfaq (Packagist) or thorsten/phpmyfaq (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-57995: phpMyFAQ privilege escalation in GroupController updatePermissions

CVE-2026-57995 · Severity: high · CVSS 8.8 · Published 2026-06-30

phpMyFAQ is an open-source FAQ software used to manage and publish knowledge bases. A security flaw allows delegated administrators with limited group-editing permissions to grant themselves or their groups any high-level administrative right. This could allow a restricted user to take full control of the FAQ system, potentially leading to the theft of sensitive data or complete service disruption.

Technologies: phpmyfaq/phpmyfaq (Packagist), thorsten/phpmyfaq (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-57995 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57995 being exploited in the wild.
How severe is CVE-2026-57995?: High severity, with a CVSS score of 8.8, published 30 June 2026.
Which products and versions are affected?: phpmyfaq/phpmyfaq (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.5; thorsten/phpmyfaq (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.5.
Is there a fix for CVE-2026-57995?: Yes. phpmyfaq/phpmyfaq (Packagist): upgrade to 4.1.5 or later; thorsten/phpmyfaq (Packagist): upgrade to 4.1.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57995 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-57995?: Check whether you run phpmyfaq/phpmyfaq (Packagist) or thorsten/phpmyfaq (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

phpmyfaq/phpmyfaq (Packagist): upgrade to 4.1.5 or later
```
composer require phpmyfaq/phpmyfaq:^4.1.5
```
thorsten/phpmyfaq (Packagist): upgrade to 4.1.5 or later
```
composer require thorsten/phpmyfaq:^4.1.5
```

Technical details

A privilege escalation vulnerability exists in phpMyFAQ's GroupController::updatePermissions due to an improper authorization check. While the system correctly restricts user-level permission assignments to only those rights held by the acting administrator, the group-level endpoint lacks this constraint. An attacker with the 'GROUP_EDIT' permission can send a crafted POST request to the /admin/group/update/permissions endpoint to assign high-privilege rights (such as SuperAdmin capabilities) to a group they belong to. Because the application fails to verify if the requester possesses the rights being assigned, the attacker inherits these new permissions through group membership. This allows for full administrative takeover. The issue is resolved in version 4.1.5.

Affected products

phpMyFAQ phpMyFAQ < 4.1.5

Identifiers

CVE-2026-57995
GHSA-pg62-f8g4-4wqh

Timeline

2026-06-14: advisory: GitHub Security Advisory published
2026-06-30: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.