CVE-2026-111902: phpMyFAQ 4.2.0-alpha before 4.2.0-beta Authorization Bypass via Comments and Attachments API

Versions reported by the vendor

Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.

• thorsten phpMyFAQ

  • 4.2.0-betanot affected
  • 4.2.0-alpha and later · before 4.2.0-betaaffected · semver

Other highest-scoring records for the same primary product.

• CVE-2026-46364phpMyFAQ - SQL Injection via User-Agent Header in BuiltinCaptcha
  38Monitor
• CVE-2026-111911phpMyFAQ 4.0.0 before 4.1.9 Authentication Bypass via WebAuthn Credential Injection
  37Monitor
• CVE-2026-66398phpMyFAQ before 4.1.6 Remote Code Execution via Configuration API
  37Monitor

Published before and after this one in the same product

• ← EarlierCVE-2026-111900Oct 17, 2026 · phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta Draft FAQ Attachment Disclosure via attachment.php
  21Monitor
• ← EarlierCVE-2026-111901Oct 17, 2026 · phpMyFAQ 4.2.0-alpha before 4.2.0-beta Unauthenticated DoS via API Pagination
  34Monitor
• Later →CVE-2026-111903Oct 17, 2026 · phpMyFAQ 4.2.0-alpha before 4.2.0-beta Stored XSS via SVG DTD Entity Bypass
  20Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const invoice = await Invoice.findById(req.params.id);2res.json(invoice);

1const invoice = await Invoice.findOne({2  id: req.params.id,3  ownerId: req.user.id,4});5if (!invoice) return res.sendStatus(404);6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.