Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-24421: CWE-862: Missing Authorization in thorsten phpMyFAQ

0
Medium
VulnerabilityCVE-2026-24421cvecve-2026-24421cwe-862
Published: Sat Jan 24 2026 (01/24/2026, 01:43:10 UTC)
Source: CVE Database V5
Vendor/Project: thorsten
Product: phpMyFAQ

Description

phpMyFAQ is an open source FAQ web application. Versions 4.0.16 and below have flawed authorization logic which exposes the /api/setup/backup endpoint to any authenticated user despite their permissions. SetupController.php uses userIsAuthenticated() but does not verify that the requester has configuration/admin permissions. Non-admin users can trigger a configuration backup and retrieve its path. The endpoint only checks authentication, not authorization, and returns a link to the generated ZIP. This issue is fixed in version 4.0.17.

AI-Powered Analysis

AILast updated: 01/24/2026, 02:06:18 UTC

Technical Analysis

The vulnerability identified as CVE-2026-24421 affects phpMyFAQ, an open-source FAQ web application, specifically versions 4.0.14 and earlier. The issue arises from improper authorization logic in the SetupController.php file, where the /api/setup/backup endpoint only verifies that a user is authenticated (via userIsAuthenticated()) but fails to confirm if the user possesses the necessary administrative or configuration permissions. Consequently, any authenticated user, regardless of their privilege level, can invoke this endpoint to trigger a backup of the application's configuration and receive a URL pointing to the generated ZIP archive containing sensitive configuration data. This exposure can lead to unauthorized disclosure of configuration details, potentially aiding attackers in further exploitation or reconnaissance. The vulnerability is classified under CWE-862 (Missing Authorization) and has a CVSS 3.1 base score of 6.5, reflecting a medium severity impact primarily on confidentiality. The flaw does not affect data integrity or system availability and does not require user interaction beyond authentication. No known exploits are currently reported in the wild. The issue was addressed and fixed in phpMyFAQ version 4.0.17 by implementing proper authorization checks to ensure only users with appropriate admin rights can access the backup functionality.

Potential Impact

For European organizations using phpMyFAQ versions below 4.0.17, this vulnerability poses a significant confidentiality risk. Unauthorized users with valid credentials—potentially low-privileged internal users or compromised accounts—can access sensitive configuration backups, which may contain database credentials, API keys, or other critical information. This exposure could facilitate further attacks such as privilege escalation, lateral movement, or data exfiltration. While the vulnerability does not directly impact system integrity or availability, the leakage of configuration data can undermine overall security posture and trustworthiness of the affected systems. Organizations in sectors with strict data protection regulations, such as finance, healthcare, or government, could face compliance issues if sensitive data is exposed. Additionally, attackers leveraging this vulnerability might gain insights into the infrastructure, increasing the risk of targeted attacks. The medium severity rating indicates a moderate but actionable threat that should be addressed promptly to prevent potential exploitation.

Mitigation Recommendations

European organizations should immediately upgrade phpMyFAQ installations to version 4.0.17 or later, where the authorization flaw is corrected. Until the upgrade can be performed, restrict access to the /api/setup/backup endpoint by implementing network-level controls such as IP whitelisting or firewall rules limiting access to trusted administrative networks. Review and enforce strict user role definitions within phpMyFAQ to minimize the number of authenticated users with access to sensitive functions. Conduct an audit of user accounts to identify and disable or remove unnecessary or inactive accounts. Monitor access logs for unusual or unauthorized attempts to invoke the backup endpoint. Additionally, consider implementing web application firewalls (WAFs) with custom rules to detect and block unauthorized access attempts to this endpoint. Regularly review and update security policies to ensure that authentication and authorization mechanisms are properly configured and tested. Finally, educate administrators and users about the importance of using strong, unique credentials to reduce the risk of account compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-22T18:19:49.175Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 697425804623b1157c76ac63

Added to database: 1/24/2026, 1:50:56 AM

Last enriched: 1/24/2026, 2:06:18 AM

Last updated: 1/24/2026, 4:06:51 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats