Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

High severity, with a CVSS score of 7.5, published 15 May 2026.

Which products and versions are affected?

phpmyfaq/phpmyfaq (Packagist) < 4.1.2; thorsten/phpmyfaq (Packagist) < 4.1.2; Thorsten phpMyFAQ < 4.1.2.

Is there a fix for This vulnerability?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is This vulnerability attacked?

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

Check whether you run phpmyfaq/phpmyfaq (Packagist), thorsten/phpmyfaq (Packagist) or Thorsten phpMyFAQ 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.

phpMyFAQ information disclosure via solution ID permission bypass

Q: Is there a fix for This vulnerability?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is This vulnerability attacked?

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

Q: Am I affected?

Check whether you run phpmyfaq/phpmyfaq (Packagist), thorsten/phpmyfaq (Packagist) or Thorsten phpMyFAQ 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.

Severity: high · CVSS 7.5 · Published 2026-05-15

phpMyFAQ is an open-source FAQ software used to manage and publish knowledge bases. A security flaw allows unauthorized individuals to bypass access controls and view the titles of private or restricted FAQ entries. This could lead to the exposure of sensitive internal information, such as project names or confidential topics, even if the full content of the articles remains protected.

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

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: High severity, with a CVSS score of 7.5, published 15 May 2026.
Which products and versions are affected?: phpmyfaq/phpmyfaq (Packagist) < 4.1.2; thorsten/phpmyfaq (Packagist) < 4.1.2; Thorsten phpMyFAQ < 4.1.2.
Is there a fix for This vulnerability?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is This vulnerability attacked?: It is attacked over the network, in a network appliance.
Am I affected?: Check whether you run phpmyfaq/phpmyfaq (Packagist), thorsten/phpmyfaq (Packagist) or Thorsten phpMyFAQ 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.

Technical details

An information disclosure vulnerability exists in phpMyFAQ's getIdFromSolutionId() method due to a lack of permission filtering. The /solution_id_{id}.html route uses this method to resolve solution IDs to internal IDs and titles, then issues a 301 redirect to a slugified URL. Because the method does not check if the FAQ is restricted to specific users or groups, an unauthenticated attacker can sequentially iterate through solution IDs to discover restricted entries. The sensitive metadata, specifically the FAQ title, is leaked through the Location header of the redirect and page canonical links. This issue is fixed in version 4.1.2.

Affected products

thorsten phpMyFAQ < 4.1.2

Timeline

2026-04-28: advisory: Original vendor advisory published (GHSA-99qv-g4x9-mgc3)
2026-05-15: disclosed: CVE-2026-46366 published
2026-06-08: other: Advisory GHSA-cqrw-j4qc-7f9w withdrawn as a duplicate

References

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