dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-46366

HIGH · 7.5 CVSS v3.1 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
phpMyFAQ before 4.1.2 contains an information disclosure vulnerability in the getIdFromSolutionId() method that lacks permission filtering, allowing unauthenticated attackers to enumerate restricted FAQ entries and read their titles via the /solution_id_{id}.html endpoint. Attackers can sequentially iterate solution IDs to discover all FAQs including those restricted to specific users or groups, leaking sensitive metadata through redirect Location headers and page canonical links.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

phpMyFAQ before 4.1.2 has an information disclosure vulnerability in the getIdFromSolutionId() method where permission checks are missing. The /solution_id_{id}.html endpoint allows unauthenticated attackers to enumerate solution IDs and access restricted FAQ titles through redirect Location headers and canonical links, leaking metadata about user-group-restricted content.

MitigationUpgrade to phpMyFAQ 4.1.2 or later which includes proper permission filtering in the getIdFromSolutionId() method. As a temporary measure, restrict or disable the /solution_id_{id}.html endpoint at the web server level until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify phpMyFAQ installation and version
    Locate the phpMyFAQ installation directory and check the version file or header files (commonly VERSION or similar file in the root directory). Compare the installed version to the affected range: any version before 4.1.2 is vulnerable.
    Affected if Installed version is before 4.1.2
  2. Verify the solution_id endpoint is accessible
    Attempt to access a URL pattern such as /solution_id_1.html or /solution_id_100.html on the phpMyFAQ server without authentication.
    Affected if The endpoint responds without requiring authentication
  3. Check for user-group-restricted FAQ content
    Log into phpMyFAQ admin panel and review FAQ categories or content for visibility settings. Look for FAQs with user group restrictions applied (typically found in the permission or visibility settings of FAQ entries).
    Affected if There are FAQs with user-group-restricted visibility that could be exposed through the endpoint
  4. Test information disclosure via redirect headers
    Send a request to /solution_id_{id}.html with a valid but restricted solution ID and observe the HTTP response headers, specifically Location headers for redirect information or canonical link headers that may leak metadata about restricted content.
    Affected if The response reveals restricted FAQ titles, metadata, or redirect information without authentication

A user is affected if phpMyFAQ version is before 4.1.2 AND the solution_id_{id}.html endpoint is accessible to unauthenticated users AND there exists user-group-restricted FAQ content that could be enumerated.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to phpMyFAQ 4.1.2 or later which includes proper permission filtering in the getIdFromSolutionId() method. As a temporary measure, restrict or disable the /solution_id_{id}.html endpoint at the web server level until the patch is applied.

Recommended fix High confidence

phpMyFAQ 4.1.2 or later

  1. 1. Backup your current phpMyFAQ installation and database before proceeding with any changes.
  2. 2. Download phpMyFAQ version 4.1.2 or later from the official repository at github.com/thorsten/phpMyFAQ
  3. 3. Replace the existing phpMyFAQ files with the new version, preserving your configuration and data files.
  4. 4. Verify the getIdFromSolutionId() method now includes proper permission filtering.
  5. 5. Test the /solution_id_{id}.html endpoint to confirm restricted FAQs are no longer accessible without proper authorization.
  6. 6. Monitor access logs for any suspicious sequential requests to solution_id endpoints that may indicate exploitation attempts.
Caveat Review changelog for any breaking changes between your current version and 4.1.2; custom templates or plugins may require updates

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46366 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data