Skip to main content
Menu
CVEs

CVE

thorsten/phpmyfaq authorization bypass in user removal requests

CVE-2026-130343EUVD-2026-126804GHSA-MMJF-PC5J-8XPR

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

5.1MediumCNA
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
0.21% · 10th percentile
18/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

phpMyFAQ has an authorization bypass in its user/request-removal API endpoint that lets a logged-in user, reachable over the network, file account removal requests on behalf of other users. An attacker who knows a victim's login name and email can send administrators a spoofed Remove User Request email, which may lead an admin to delete the victim's account and data.

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

Original description

phpMyFAQ 3.2.5 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the user/request-removal API endpoint that lets authenticated users file account removal requests as other users. The ownership check calls getUserById() with the attacker-supplied userId on the session user object, so it compares the input against the target's own record. Attackers who know a victim's login name and email can submit that userId, loginname, and email, sending administrators a spoofed Remove User Request email. This may lead an admin to delete the victim's account and data.

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Affects Packagist packages
  • Severity5.1/10CVSS 5.1
  • 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 37 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-130343 (phpMyFAQ 3.2.5 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Authorization Bypass via request-removal), 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-130343 (entry last updated 2026-11-17):
Affected:
- Packagist package thorsten/phpmyfaq: from 3.2.5, 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-130343 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130343 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-42c6-wxqw-2rv6
- https://github.com/thorsten/phpMyFAQ/commit/30997574d7c00b4e2d7121cf1653fb244c63dd9e
- 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-3.2.5-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-authorization-bypass-via-request-removal
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-130343
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-130343"}.

Timeline

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

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

  4. Record last updated

Affected versions

  • From 3.2.5 · fixed in 4.1.12; From 4.2.0-alpha · fixed in 4.2.0-RC.2

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

Is CVE-2026-130343 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-130343?

thorsten/phpmyfaq (Packagist): from 3.2.5 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-130343?

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

More CVEs