Authenticated code execution via trusted updater path
Published Jul 27, 2026 · Updated Jul 27, 2026
Remote code execution in phpMyFAQ before 4.1.6 allows remote authenticated users to execute PHP as the web server user. The configuration API accepts upgrade.lastDownloadedPackage, and the updater trusts that attacker-selected ZIP path before extracting its phpMyFAQ payload into the application root. Exploitation requires both CONFIGURATION_EDIT and ATTACHMENT_ADD administrator privileges and permits persistent PHP file writes and code execution.
Summary
What happened
Remote code execution in phpMyFAQ before 4.1.6 allows remote authenticated users to execute PHP as the web server user. The configuration API accepts upgrade.lastDownloadedPackage, and the updater trusts that attacker-selected ZIP path before extracting its phpMyFAQ payload into the application root. Exploitation requires both CONFIGURATION_EDIT and ATTACHMENT_ADD administrator privileges and permits persistent PHP file writes and code execution.
The record
- CVE
- CVE-2026-66398
- Published
- Jul 27, 2026
- Updated
- Jul 27, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-829, CWE-494, T1505.003
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jul 27, 2026CVE publishedPublication date reported by the CVE source.
- Jul 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.1.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream authenticated updater-path reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo