CVE-2026-76205: phpMyFAQ before 4.1.7 contains a SQL injection vulnerability in the glossary create and update endpoints cause

Q: How do I fix CVE-2026-76205?

phpmyfaq: upgrade to 4.1.7. Exact commands for each OS are on this page.

Q: Is CVE-2026-76205 being exploited?

CVE-2026-76205 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-76205 affect?

CVE-2026-76205 affects phpmyfaq. Severity is high (CVSS 8.1). phpMyFAQ before 4.1.7 contains a SQL injection vulnerability in the glossary create and update endpoints caused by truncating an escaped string before embedding it in a SQL literal. Authenticated users with glossary add or edit permissions

Q: How urgent is CVE-2026-76205?

Priority 43/100. High severity; Public exploit reference

This month

HIGH 8.1UPGRADE

CVE-2026-76205 is a high-severity flaw (CVSS 8.1) affecting phpmyfaq. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

phpMyFAQ before 4.1.7 contains a SQL injection vulnerability in the glossary create and update endpoints caused by truncating an escaped string before embedding it in a SQL literal. Authenticated users with glossary add or edit permissions can craft a payload with a dangling backslash to escape the closing quote and inject arbitrary SQL commands to read sensitive database information.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-89
Published	2026-08-19
Last modified	2026-09-01

Publisher (CNA): VulnCheck · Vendor: phpmyfaq

Last updated 2026-09-01 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-19 14:17 UTCPublished CVE record published
2026-09-01 15:23 UTCUpdated Record last modified

phpmyfaq phpmyfaq UPGRADE

Affected: < 4.1.7

Fixed in: 4.1.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy phpmyfaq || rpm -q phpmyfaq || phpmyfaq --version

2. UPGRADE to 4.1.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade phpmyfaq

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade phpmyfaq

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-76205?

phpmyfaq: upgrade to 4.1.7. Exact commands for each OS are on this page.

Is CVE-2026-76205 being exploited?

CVE-2026-76205 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-76205 affect?

CVE-2026-76205 affects phpmyfaq. Severity is high (CVSS 8.1). phpMyFAQ before 4.1.7 contains a SQL injection vulnerability in the glossary create and update endpoints caused by truncating an escaped string before embedding it in a SQL literal. Authenticated users with glossary add or edit permissions

How urgent is CVE-2026-76205?

Priority 43/100. High severity; Public exploit reference

Related CVEs

CVE-2026-34728 HIGH 8.7 UPGRADE phpMyFAQ is an open source FAQ web application
CVE-2026-32629 MEDIUM 6.1 UPGRADE phpMyFAQ is an open source FAQ web application
CVE-2026-34729 MEDIUM 6.1 UPGRADE phpMyFAQ is an open source FAQ web application
CVE-2026-76208 HIGH 8.2 UPGRADE phpMyFAQ versions 3.1.0 through 4.1.6 contain an authentication bypass vulnerability in AuthLdap::create()
CVE-2026-75920 MEDIUM 5.3 UPGRADE phpMyFAQ before v4.1.6 writes content backup ZIP archives to the web-accessible document root at content.zip,

References

← Back to latest CVEs