Session cookie disclosure via missing Secure flag
Published Dec 11, 2022 · Updated Apr 14, 2025
Sensitive cookie handling in phpMyFAQ before 3.1.9 allows remote attackers to read session cookies via HTTPS responses. Bootstrap.php and Session.php derive the cookie Secure attribute from HTTPS detection; affected releases leave it unset, allowing browsers to send the cookie over HTTP. An attacker able to observe downgraded or mixed HTTP traffic can obtain the session cookie, causing session confidentiality loss without demonstrated integrity or availability impact.
Summary
What happened
Sensitive cookie handling in phpMyFAQ before 3.1.9 allows remote attackers to read session cookies via HTTPS responses. Bootstrap.php and Session.php derive the cookie Secure attribute from HTTPS detection; affected releases leave it unset, allowing browsers to send the cookie over HTTP. An attacker able to observe downgraded or mixed HTTP traffic can obtain the session cookie, causing session confidentiality loss without demonstrated integrity or availability impact.
The record
- CVE
- CVE-2022-4409
- Published
- Dec 11, 2022
- Updated
- Apr 14, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-614, CWE-311, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record 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=unspecified <3.1.9
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
- Huntr CVE-2022-4409 proof of conceptproof of concept · unverified
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