How severe is CVE-2026-24422?

CVE-2026-24422 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2026-24422 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (30th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-24422?

CVE-2026-24422 affects Phpmyfaq. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-24422?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-24422 have an EU (EUVD) identifier?

Yes. CVE-2026-24422 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-4257.

When was CVE-2026-24422 published?

CVE-2026-24422 was published on 2026-01-24 and last updated on 2026-06-17.

CVE-2026-24422

CVE-2026-24422 is a medium-severity vulnerability in Phpmyfaq with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-200.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
EPSS exploit prediction: 0% (30th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-4257
Weakness: CWE-200
Affected product: Phpmyfaq
Published: 2026-01-24
Last modified: 2026-06-17

Description

phpMyFAQ is an open source FAQ web application. In versions 4.0.16 and below, multiple public API endpoints improperly expose sensitive user information due to insufficient access controls. The OpenQuestionController::list() endpoint calls Question::getAll() with showAll=true by default, returning records marked as non-public (isVisible=false) along with user email addresses, with similar exposures present in comment, news, and FAQ APIs. This information disclosure vulnerability could enable attackers to harvest email addresses for phishing campaigns or access content that was explicitly marked as private. This issue has been fixed in version 4.0.17.

Frequently asked questions

What is CVE-2026-24422?: phpMyFAQ is an open source FAQ web application. In versions 4.0.16 and below, multiple public API endpoints improperly expose sensitive user information due to insufficient access controls. The OpenQuestionController::list() endpoint calls Question::getAll() with showAll=true by default, returning records marked as non-public (isVisible=false) along with user email addresses, with similar exposures present in comment, news, and FAQ APIs. This information disclosure vulnerability could enable attackers to harvest email addresses for phishing campaigns or access content that was explicitly marked as private. This issue has been fixed in version 4.0.17.
How severe is CVE-2026-24422?: CVE-2026-24422 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2026-24422 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (30th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-24422?: CVE-2026-24422 affects Phpmyfaq. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-24422?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-24422 have an EU (EUVD) identifier?: Yes. CVE-2026-24422 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-4257.
When was CVE-2026-24422 published?: CVE-2026-24422 was published on 2026-01-24 and last updated on 2026-06-17.

References

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j4rc-96xj-gvqc

Affected products (1)

cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*

More vulnerabilities in Phpmyfaq

CVE-2023-5865 — Critical (CVSS 9.8): Insufficient Session Expiration in GitHub repository thorsten/phpmyfaq prior to 3.2.2.
CVE-2023-5227 — Critical (CVSS 9.8): Unrestricted Upload of File with Dangerous Type in GitHub repository thorsten/phpmyfaq prior to 3.1.8.
CVE-2023-4006 — Critical (CVSS 9.8): Improper Neutralization of Formula Elements in a CSV File in GitHub repository thorsten/phpmyfaq prior to 3.1.16.
CVE-2023-2429 — Critical (CVSS 9.8): Improper Access Control in GitHub repository thorsten/phpmyfaq prior to 3.1.13.
CVE-2023-0311 — Critical (CVSS 9.8): Improper Authentication in GitHub repository thorsten/phpmyfaq prior to 3.1.10.
CVE-2023-0307 — Critical (CVSS 9.8): Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.10.

All CVEs affecting Phpmyfaq →

Other CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities

CVE-2026-27604 — Critical (CVSS 10.0): FOSSBilling is a free, open-source billing and client management system. Starting in version 0.5.4 and prior to version…
CVE-2026-40965 — Critical (CVSS 10.0): Cloud Foundry UAA versions v76.12.0 through v78.12.0 are vulnerable to a private key exposure. The server contains a…
CVE-2026-42826 — Critical (CVSS 10.0): Exposure of sensitive information to an unauthorized actor in Azure DevOps allows an unauthorized attacker to disclose…
CVE-2025-29270 — Critical (CVSS 10.0): Incorrect access control in the realtime.cgi endpoint of Deep Sea Electronics devices DSE855 v1.1.0 to v1.1.26 allows…
CVE-2025-61481 — Critical (CVSS 10.0): An issue in MikroTik RouterOS v.7.14.2 and SwOS v.2.18 exposes the WebFig management interface over cleartext HTTP by…
CVE-2025-53624 — Critical (CVSS 10.0): The Docusaurus gists plugin adds a page to your Docusaurus instance, displaying all public gists of a GitHub user.…

Browse all CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities →