External risk intelligence

phpMyFAQ Multisite Authorization Bypass Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-130369

phpMyFAQ is a web-based frequently asked questions application. By design, such applications are deployed as public-facing web services to provide documentation or support portals to users. The vulnerability exists within the application's API endpoints, which are exposed as part of the standard web interface, making it likely that the vulnerable surface is reachable from the internet in common deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability has been identified in phpMyFAQ, affecting its multisite capabilities. This issue allows unauthorized access and modification of account passkeys across different tenants, potentially enabling administrative takeover. The main concern is confirming relevance and exposure to your deployments.

  • Bypass authorization to hijack accounts.
  • Affects multisite phpMyFAQ deployments.
  • Confirm exposure and assess potential impact.

Attack Path

How an attacker could exploit the issue

An attacker can compromise user accounts on different tenants within a multisite phpMyFAQ deployment. By initiating a WebAuthn preparation on one tenant, an attacker can then replay this session against another tenant's registration API to replace existing passkeys. This attack allows an unauthorized user to gain administrative access to other accounts.

  • Attacker requires network access.
  • Vulnerability triggered via API request.
  • Risk of unauthorized account takeover.

Live Threat

Current exploitation, exposure, and threat context

In multisite phpMyFAQ deployments, an authorization bypass could allow an attacker to gain administrative control over accounts on different tenants. This occurs when an attacker, after initiating a WebAuthn registration for a login on one tenant, replays the session against a different tenant or the master instance to overwrite user passkeys. The advisory does not indicate that PII or other specific data types are at risk beyond account credentials.

  • Account credentials could be compromised.
  • Attackers can replay session data.
  • Unauthorized administrative access is possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

In real-world scenarios, platform or application owners are likely responsible for phpMyFAQ, with vendor management teams needing to engage if it's a third-party service. The immediate practical step is to identify all instances, confirm their reachability and criticality, and then prioritize remediation by coordinating with the vendor or planning a maintenance window.

  • Platform/application owners must address this.
  • Verify all phpMyFAQ instances and reachability.
  • Plan remediation with vendor coordination.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is phpMyFAQ?

phpMyFAQ is an open-source, web-based software used to build and manage searchable frequently asked questions and support portals. Organizations deploy it to provide documentation or self-service help to their users. Because it is designed to be accessible to the public for information gathering, it functions as a central repository for knowledge bases, often running on web servers that serve multiple distinct groups or tenants simultaneously.

What is the vulnerability in CVE-2026-130369?

This vulnerability is an authorization bypass, categorized as CWE-639, which involves the improper authorization of user-controlled session identifiers. In plain terms, the software fails to correctly isolate user sessions between different tenants. This allows a user to trick the system into believing they have the authority to modify security settings, such as passkeys, for an account on a completely different tenant than the one where they started their session.

How is the CVE-2026-130369 flaw triggered?

An attacker triggers this by first initiating a WebAuthn preparation process on one tenant and then replaying that same session data against a different tenant or the master instance via the API. Note that this requires specific interaction with the WebAuthn registration endpoint; simply browsing the public-facing FAQ pages without attempting these API-level session manipulations will not trigger the account takeover.

Is my phpMyFAQ deployment at risk?

According to Halo Surface Signal, this vulnerability is considered likely to be reachable from the internet. Because phpMyFAQ is built to be a public-facing support portal, its API endpoints are usually exposed to the web. If your deployment uses the affected multisite configuration, you should assume the risk is relevant, as the application's design requires it to be reachable by the very users who might attempt such an unauthorized access request.

How should I respond to this threat?

Start by identifying all instances of phpMyFAQ within your environment to determine if they are configured for multisite use. Once you have a complete inventory, assess their reachability. If you are running an affected version, prioritize planning a maintenance window to apply the necessary updates provided by the software vendor to close the authorization gap.

References