dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-57994

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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.5 applies inconsistent active=yes and publication-date filtering across its public FAQ API endpoints, allowing unauthenticated attackers to retrieve inactive (draft or review-only) FAQ content. Specifically, GET /api/v3.1/faq/{categoryId}/{faqId} returns the inactive FAQ title and full answer, while GET /api/v3.1/faqs/tags/{tagId} and GET /api/v4.0/faqs/tags/{tagId} return the inactive FAQ title and answer preview, disclosing non-public content.

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 versions before 4.1.5 have inconsistent authorization filtering across public API endpoints. The /api/v3.1/faq/{categoryId}/{faqId} endpoint returns full inactive FAQ content (title and complete answer), while /api/v3.1/faqs/tags/{tagId} and /api/v4.0/faqs/tags/{tagId} return title and answer previews—all without requiring authentication and without enforcing active=yes or publication-date checks that other endpoints correctly apply.

MitigationUpgrade to phpMyFAQ version 4.1.5 or later which applies consistent active and publication-date filtering across all API endpoints to prevent unauthorized disclosure of draft or review-only FAQ content.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed phpMyFAQ version
    Locate the version file (typically VERSION or src/phpMyFAQ/Version.php) or check the admin dashboard footer for the version number
    Affected if The installed version is below 4.1.5 (e.g., 4.1.4, 4.1.0, 3.x, etc.)
  2. Verify API endpoint accessibility
    Send unauthenticated HTTP GET requests to /api/v3.1/faq/{categoryId}/{faqId}, /api/v3.1/faqs/tags/{tagId}, and /api/v4.0/faqs/tags/{tagId}
    Affected if The endpoints return HTTP 200 responses instead of 401/403 authentication errors
  3. Confirm inactive FAQ content exposure
    Query the API endpoints using IDs known to correspond to inactive FAQs (active='no' or future publication dates) and examine the response body
    Affected if The endpoints return complete FAQ titles, answers, or previews for inactive content that should be restricted

You are affected if your phpMyFAQ version is below 4.1.5 AND the vulnerable API endpoints are accessible and return content from inactive or unpublished FAQs without authentication.

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 version 4.1.5 or later which applies consistent active and publication-date filtering across all API endpoints to prevent unauthorized disclosure of draft or review-only FAQ content.

Recommended fix High confidence

phpMyFAQ 4.1.5

  1. 1. Backup your existing phpMyFAQ installation and database before proceeding with any upgrade.
  2. 2. Download phpMyFAQ version 4.1.5 or later from the official phpMyFAQ repository (github.com/thomaskaiser/phpMyFAQ) or the official website.
  3. 3. Replace the existing phpMyFAQ files with the new version, preserving your configuration file (typically inc/phpMyFAQ/inc/data.php or similar configuration location).
  4. 4. Run the database upgrade script if included (usually accessible via /setup or admin interface).
  5. 5. Verify the fix by testing the affected API endpoints: GET /api/v3.1/faq/{categoryId}/{faqId}, GET /api/v3.1/faqs/tags/{tagId}, and GET /api/v4.0/faqs/tags/{tagId} to confirm inactive FAQs are no longer returned to unauthenticated users.
  6. 6. Clear any caches and restart web server services if required.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57994 — 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-57994 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