Skip to main content
Menu
CVEs

CVE

thorsten/phpmyfaq email address disclosure in public FAQ REST API

CVE-2026-130353

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.1.12, 4.2.0-RC.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.1.12, 4.2.0-RC.2.

Published
Last modified
Reference
Last checked
34/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

phpMyFAQ, an FAQ web application, has an information disclosure flaw in its public FAQ REST API. Remote attackers without logging in can query the FAQ endpoints to collect author names and e-mail addresses, including those of users who opted out of author visibility.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability in its public FAQ REST API that exposes author names and e-mail addresses to unauthenticated callers. Attackers can query the faq and paginated faqs endpoints to bulk-harvest e-mails and de-anonymise users who opted out of GDPR author visibility.

cve.now Index

34Pcve.now Index 34 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects Packagist packages
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 79 if added to CISA KEV
  • Would score about 74 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.1.12, 4.2.0-RC.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130353 (phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 FAQ API Email Disclosure), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130353 (entry last updated 2026-11-17):
Affected:
- Packagist package thorsten/phpmyfaq: fixed in 4.1.12; from 4.2.0-alpha, fixed in 4.2.0-RC.2
Fixed versions: 4.1.12, 4.2.0-RC.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130353 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130353 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8c38-gwr2-p787
- https://github.com/thorsten/phpMyFAQ/commit/579d6606f7d7f723ab74b69bd31a8dee1f859013
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.1.12
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
- https://www.vulncheck.com/advisories/phpmyfaq-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-faq-api-email-disclosure
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130353
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130353"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Patch
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130353

Is CVE-2026-130353 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130353?

thorsten/phpmyfaq (Packagist): before 4.1.12; from 4.2.0-alpha before 4.2.0-RC.2.Source: cve.now feed data

How do I fix CVE-2026-130353?

Upgrade to a fixed version: 4.1.12, 4.2.0-RC.2.Source: cve.now feed data