Read the docs

Cross-site request forgery in phpMyFAQ update-database endpoint

Priority LOW 36CWE-352Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Passive
Attack complexity
Low
Attack requirements
None
Impact type
Tampering
Confidentiality · integrity · availability
None · Low · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-352.

Summary

phpMyFAQ from 4.0.0 before 4.1.9 contains a cross-site request forgery flaw in the POST /admin/api/update-database endpoint, which runs database migrations without validating a CSRF token (CWE-352). An attacker can lure a logged-in user with the CONFIGURATION_EDIT permission into submitting a crafted cross-site request. The resulting migrations may impact database integrity or availability.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

phpMyFAQ 4.0.0 before 4.1.9 contains a cross-site request forgery vulnerability in the POST /admin/api/update-database endpoint, which executes database migrations without validating a CSRF token. Attackers can lure a logged-in user with the CONFIGURATION_EDIT permission into submitting a crafted cross-site request, triggering migrations that may impact database integrity or availability.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00115 1st percentileScored 2026-11-07
Fix Fixed phpMyFAQ (thorsten): 4.1.9

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
thorstenphpMyFAQ4.0.0 to before 4.1.94.1.9Patch availableCNA
  • phpMyFAQ Vendorthorsten Affected 4.0.0 to before 4.1.9 Fixed in 4.1.9 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*——thorsten
  • cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:* Versions — — ·thorsten

Remediation

Upgrade phpMyFAQ to version 4.1.9, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA phpMyFAQ (thorsten) Fixed in 4.1.9

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    thorsten phpMyFAQ 4.1.9

    14 records Highest priority Priority HIGH 5 HIGH, 6 MEDIUM, 3 LOW

    Other records, highest priority first

    • TI-2026-76118 Authentication bypass in phpMyFAQ via WebAuthn credential injectionPriority HIGH 81
    • TI-2026-76115 Authorization bypass in phpMyFAQ REST API edits restricted FAQsPriority HIGH 73
    • TI-2026-76092 phpMyFAQ e-mail change lacks password check, enabling takeoverPriority HIGH 73

Timeline

  1. 2026-10-18 Threatist record created from CVE-2026-111907
  2. 2026-10-18 Alias added: GHSA-mm6v-fm3q-x3xw
  3. 2026-10-18 Priority changed: MEDIUM → LOW
  4. 2026-10-19 CISA SSVC decision points changed

References

  • TI-2023-00296 Improper Authentication in thorsten/phpmyfaq CVSS 3.1CRITICAL 9.8
  • TI-2026-76118 Authentication bypass in phpMyFAQ via WebAuthn credential injection CVSS 4.0CRITICAL 9.3
  • TI-2026-32868 phpMyFAQ - Unauthenticated Two-Factor Authentication Brute-Force via /admin/check Endpoint CVSS 4.0CRITICAL 9.3
  • TI-2026-76108 Unauthenticated denial of service in phpMyFAQ API pagination CVSS 4.0HIGH 8.7
  • TI-2026-53313 phpMyFAQ 3.1.0 through 4.1.6 Authentication Bypass via LDAP CVSS 4.0HIGH 8.8
  • TI-2026-34083 phpMyFAQ - Unauthenticated Information Disclosure via getIdFromSolutionId Permission Bypass CVSS 4.0HIGH 8.7
See all 224 →

Sources