Skip to main content
Menu
CVEs

CVE

thorsten/phpmyfaq authorization bypass in FAQ update API

CVE-2026-130356EUVD-2026-126791GHSA-2F6H-RH8G-H6PH

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

5.3MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 4.2.0-RC.2
Who is exposed
Not reported

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

Published
Last modified
Reference
Last checked
0.19% · 8th percentile
33/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: partial

Summary

phpMyFAQ has an authorization bypass that lets a remote attacker with a low-privilege, category- or language-restricted editor account change the visibility rules and tags of any FAQ. By sending crafted update requests with a target FAQ ID and an untranslated language code, the attacker can expose restricted FAQs, wipe tags, or overwrite orphaned FAQs.

Written by a model from the sources below. Verify against them.

Original description

phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass that lets category- or language-restricted editors rewrite visibility ACLs and tags of any FAQ. Attackers send faq/update requests with a target faqId and an untranslated lang to expose restricted FAQs, wipe tags, or overwrite orphaned FAQs.

cve.now Index

33Pcve.now Index 33 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Affects Packagist packages
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 52 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 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-130356 (phpMyFAQ 4.2.0-alpha.2 before 4.2.0-RC.2 Authorization Bypass via /admin/api/faq/update), 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-130356 (entry last updated 2026-11-17):
Affected:
- Packagist package thorsten/phpmyfaq: from 4.2.0-alpha.2, fixed in 4.2.0-RC.2
Fixed versions: 4.2.0-RC.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130356 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130356 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-cch2-977x-6vqj
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
- https://www.vulncheck.com/advisories/phpmyfaq-4.2.0-alpha.2-before-4.2.0-rc.2-authorization-bypass-via-admin-api-faq-update
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-130356
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-130356"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Repository
  2. Link

Corrections

None so far.

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

Questions about CVE-2026-130356

Is CVE-2026-130356 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130356?

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

How do I fix CVE-2026-130356?

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

More CVEs