TI-2026-34081 Aliases CVE-2026-46364 GHSA-289f-fq7w-6q2w

phpMyFAQ - SQL Injection via User-Agent Header in BuiltinCaptcha

MEDIUM 51CWE-89Published 2026-05-15 · Updated 2026-11-08

Key facts

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

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-89.

Summary

phpMyFAQ before 4.1.2 contains an unauthenticated SQL injection vulnerability in BuiltinCaptcha::garbageCollector() and BuiltinCaptcha::saveCaptcha() methods that interpolate unsanitized User-Agent headers into DELETE and INSERT queries. Unauthenticated attackers can exploit the public GET /api/captcha endpoint by crafting malicious User-Agent headers to perform time-based blind SQL injection, extracting sensitive data including user credentials, admin tokens, and SMTP credentials from the database.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV

EPSS 0.01709 77th percentileScored 2026-11-07

Fix Fixed phpmyfaq (thorsten): 4.1.2thorsten/phpmyfaq (Packagist): 4.1.2+1 more product

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation: None
Automatable: Yes
Technical impact: Total

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

Affected products

Vendor	Product	Affected versions	Fixed in	Status	Source
thorsten	phpmyfaq	before 4.1.2	4.1.2	Patch available	CNA
—	thorsten/phpmyfaq (Packagist)	before 4.1.2	4.1.2	Patch available	GHSA-289f-fq7w-6q2w
—	phpmyfaq/phpmyfaq (Packagist)	before 4.1.2	4.1.2	Patch available	GHSA-289f-fq7w-6q2w

phpmyfaq Vendorthorsten Affected before 4.1.2 Fixed in 4.1.2 Patch available CNA
thorsten/phpmyfaq (Packagist) Vendor— Affected before 4.1.2 Fixed in 4.1.2 Patch available GHSA-289f-fq7w-6q2w
phpmyfaq/phpmyfaq (Packagist) Vendor— Affected before 4.1.2 Fixed in 4.1.2 Patch available GHSA-289f-fq7w-6q2w

CPE names Threatist (inferred) · 1

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

CPE	Versions	Role	Vendor
cpe:2.3:a:phpmyfaq:phpmyfaq::::::::	—	—	thorsten

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

Remediation

Fix · CNA phpmyfaq (thorsten) Fixed in 4.1.2
Fix · GHSA-289f-fq7w-6q2w thorsten/phpmyfaq (Packagist) Fixed in 4.1.2 Advisory →
Fix · GHSA-289f-fq7w-6q2w phpmyfaq/phpmyfaq (Packagist) Fixed in 4.1.2 Advisory →

Fixed in the same release

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

Release · 2026-05-15
thorsten phpmyfaq 4.1.2
13 records Highest priority Priority HIGH 5 HIGH, 8 MEDIUM
Other records, highest priority first
- TI-2026-32868 phpMyFAQ - Unauthenticated Two-Factor Authentication Brute-Force via /admin/check EndpointPriority HIGH 81
- TI-2026-34083 phpMyFAQ - Unauthenticated Information Disclosure via getIdFromSolutionId Permission BypassPriority HIGH 77
- TI-2026-34084 phpMyFAQ - Stored XSS via Utils::parseUrl() in Comment RenderingPriority HIGH 69
Show all 13 records →

Timeline

2026-10-02 Threatist record created from CVE-2026-46364
2026-10-03 Alias added: GHSA-289f-fq7w-6q2w

References

Patch 1

https://github.com/thorsten/phpMyFAQ/commit/b9f25109fddb38eee19987183798638d07943f92

Advisory 2

Other 1

https://github.com/thorsten/phpMyFAQ

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

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences