Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-49205: CWE-862: Missing Authorization in thorsten phpMyFAQ

0
Medium
VulnerabilityCVE-2026-49205cvecve-2026-49205cwe-862
Published: Thu Jun 18 2026 (06/18/2026, 21:12:34 UTC)
Source: CVE Database V5
Vendor/Project: thorsten
Product: phpMyFAQ

Description

phpMyFAQ versions prior to 4.1.4 have a missing authorization vulnerability in several API endpoints related to category, FAQ, and question creation and update. These endpoints rely only on a shared API key token check rather than verifying individual user permissions, potentially allowing unauthorized write operations. This issue was fixed in version 4.1.4.

CVSS v3.1

Score 6.5medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected software

GitHub Actionsmore threats →ai
thorsten/phpMyFAQ
pkg:github/thorsten/phpMyFAQ
Affected versions
<4.1.4

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: 06/18/2026, 22:20:32 UTC

Technical Analysis

phpMyFAQ, an open source FAQ web application, has a missing authorization vulnerability (CWE-862) in versions before 4.1.4. While a previous CVE (CVE-2026-24421) addressed authorization in the BackupController by enforcing user permission checks, this fix was not applied to four other write endpoints in the public API: POST /api/v4.0/category, POST /api/v4.0/faq, PUT /api/v4.0/faq, and POST /api/v4.0/question. These endpoints only validate a shared API key token rather than individual user role permissions, which could allow unauthorized users with the API key to perform write operations. The vulnerability is fixed in version 4.1.4.

Potential Impact

An attacker with access to the shared API key could perform unauthorized write operations on categories, FAQs, and questions via the affected API endpoints. This could lead to unauthorized content creation or modification. The CVSS score is 6.5 (medium severity) with high confidentiality impact but no integrity or availability impact.

Mitigation Recommendations

Upgrade phpMyFAQ to version 4.1.4 or later, where the missing authorization checks have been properly implemented on all affected API endpoints. No other mitigation is indicated by the vendor advisory.

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
GitHub_M
Date Reserved
2026-05-28T03:42:34.340Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a346bc9f198dc38c1a1cd9a

Added to database: 6/18/2026, 10:06:01 PM

Last enriched: 6/18/2026, 10:20:32 PM

Last updated: 6/19/2026, 12:20:34 AM

Views: 7

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