CVE-2026-46359: phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields

high Affects phpmyfaq/phpmyfaq, thorsten/phpmyfaq. Feed 2026.10.29.1, updated 2026-10-28; published ; advisory modified .

phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields

Package
phpmyfaq/phpmyfaq Composer
Affected versions
<4.1.2
Fixed in
4.1.2
Severity
high  CVSS 7.5
Exploitation
not on CISA KEV · EPSS 0% (18.3th percentile)
Published
2026-05-06
Source
osv.dev

References

phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields

Package
thorsten/phpmyfaq Composer
Affected versions
<4.1.2
Fixed in
4.1.2
Severity
high  CVSS 7.5
Exploitation
not on CISA KEV · EPSS 0% (18.3th percentile)
Published
2026-05-06
Source
osv.dev

References

CWE-89
NVD recordphpmyfaq/phpmyfaq advisoriesthorsten/phpmyfaq advisories

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked

Related advisories