Skip to main content
EPSS 0.4%top 74%

CVE-2026-76215: Missing Authorization in thorsten phpMyFAQ

0
Medium
Published: 08/19/2026 (08/19/2026, 14:02:00 UTC)
Source: CVE Database V5
Vendor/Project: thorsten
Product: phpMyFAQ

Description

phpMyFAQ versions prior to 4.1.7 contain a missing authorization vulnerability where parent FAQ visibility checks are not enforced before returning child resources such as comments and attachments. This allows unauthenticated attackers to access restricted comment text, commenter email addresses, and attachment filenames for FAQ entries they cannot directly access.

CVSS v4.0

Score 6.9medium

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
Low
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Affected software

thorsten

phpMyFAQ

Affected versions
>=0 <4.1.7
GitHub Actionsmore threats →ai
thorsten/phpMyFAQ
pkg:github/thorsten/phpMyFAQ
Affected versions
<4.1.7

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/11/2026, 08:48:19 UTC

Technical Analysis

CVE-2026-76215 is a missing authorization vulnerability in phpMyFAQ before version 4.1.7. The software fails to verify parent FAQ visibility before returning child resources, including comments and attachments, via API endpoints. As a result, unauthenticated attackers can retrieve sensitive information such as restricted comment text, email addresses of commenters, and attachment filenames associated with FAQ records that should be inaccessible to them.

Potential Impact

The vulnerability allows unauthenticated attackers to access sensitive data that should be restricted, including comment contents, email addresses of commenters, and attachment filenames related to FAQ entries. This exposure could lead to privacy violations and information disclosure without requiring any authentication.

Mitigation Recommendations

Upgrade phpMyFAQ to version 4.1.7 or later where this authorization issue has been fixed. No other mitigation guidance is provided. Patch status is confirmed by the version boundary indicating the fix in 4.1.7.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-08-19T11:35:13.689Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a85bc76acd9273b492f498e

Added to database: 08/19/2026, 14:23:50 UTC

Last enriched: 09/11/2026, 08:48:19 UTC

Last updated: 10/04/2026, 10:02:29 UTC

Views: 64

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses