Skip to main content
Menu
CVEs

CVE

thorsten/phpmyfaq authorization bypass in user rights update API

Only affects phpMyFAQ 4.2.0-alpha.2 through 4.2.0-RC.2 with security.permLevel set to medium and group category restrictions configured. Fixed in 4.2.0-RC.2.

CVE-2026-130357

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

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

7.0HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.2.0-RC.2
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. security.permLevel is set to medium, with group category restrictions configured phpMyFAQ 4.2.0-alpha.2 through 4.2.0-RC.2 / current main

Published
Last modified
Reference
Last checked
25/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

An attacker who already has high-privilege login access to the affected phpMyFAQ releases can remotely use the user update-rights API to remove category restrictions from group rights. This lets them edit, publish or delete FAQs in categories they were meant to be kept out of.

Original description

phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an improper authorization vulnerability in updateUserRights that lets USER_EDIT admins drop category restrictions on group rights. Attackers can re-save rights through the user update-rights API to convert category-restricted group rights into global direct rights, then edit, publish or delete FAQs in withheld categories.

Who should check

Teams running phpMyFAQ 4.2.0-alpha.2 before 4.2.0-RC.2 with security.permLevel=medium and category-restricted group rights.

“Affecting phpMyFAQ >= 4.2.0-alpha.2, < 4.2.0-RC.2”

vulncheck.com

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Packagist packages
  • Severity7/10CVSS 7.0
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    security.permLevel is set to medium, with group category restrictions configured phpMyFAQ 4.2.0-alpha.2 through 4.2.0-RC.2 / current main
  • 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-130357 (phpMyFAQ 4.2.0-alpha.2 before 4.2.0-RC.2 Privilege Escalation via updateUserRights), 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-130357 (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.
Conditions (all must be true for the bug to be hit):
- security.permLevel is set to medium, with group category restrictions configured (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-cg5x-q2hj-hw3j)
- phpMyFAQ 4.2.0-alpha.2 through 4.2.0-RC.2 / current main (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-cg5x-q2hj-hw3j)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-130357 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130357 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-cg5x-q2hj-hw3j
- 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-privilege-escalation-via-updateuserrights
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-130357
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-130357"}.

Timeline

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

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-130357

Is CVE-2026-130357 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

What does this mean?

A non-SuperAdmin admin with USER_EDIT rights can convert category-restricted group rights into global direct rights. This lets them edit, unpublish, publish or delete FAQs and attachments in categories that were meant to be withheld from them.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-130357?

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

Am I affected, and how do I check?

Versions 4.2.0-alpha.2 through 4.2.0-RC.2 and current main are affected, but only when security.permLevel is set to medium with group category restrictions configured. Check the security.permLevel setting in the phpMyFAQ configuration to see which setup is in use.Source: github.com, vulncheck.com

How do I fix CVE-2026-130357?

Upgrade to phpMyFAQ 4.2.0-RC.2, the fixed version. The sources name no vendor patch ids or workaround.Source: github.com, vulncheck.com