CVE-2026-75918: phpMyFAQ before 4.1.7 stores password reset tokens in a publicly accessible tracking file when user tracking i

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

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

Q: Is CVE-2026-75918 being exploited?

CVE-2026-75918 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-75918 affect?

CVE-2026-75918 affects phpmyfaq. Severity is high (CVSS 8.8). phpMyFAQ before 4.1.7 stores password reset tokens in a publicly accessible tracking file when user tracking is enabled. Unauthenticated attackers can read the tracking file at content/core/data/trackingDDMMYYYY to extract reset tokens and

Q: How urgent is CVE-2026-75918?

Priority 46/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2026-75918 is a high-severity flaw (CVSS 8.8) 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 stores password reset tokens in a publicly accessible tracking file when user tracking is enabled. Unauthenticated attackers can read the tracking file at content/core/data/trackingDDMMYYYY to extract reset tokens and replay them against the password reset API to take over user accounts.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-200
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:30 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-75918?

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

Is CVE-2026-75918 being exploited?

CVE-2026-75918 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-75918 affect?

CVE-2026-75918 affects phpmyfaq. Severity is high (CVSS 8.8). phpMyFAQ before 4.1.7 stores password reset tokens in a publicly accessible tracking file when user tracking is enabled. Unauthenticated attackers can read the tracking file at content/core/data/trackingDDMMYYYY to extract reset tokens and

How urgent is CVE-2026-75918?

Priority 46/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