CVE-2022-4409 json
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in thorsten/phpmyfaq
published 2022-12-11 3 y ago modified 2026-06-17 4 mo ago also GHSA-wpgc-5cr5-h9gg , EUVD-2022-7764
- cvss
- 6.3
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository thorsten/phpmyfaq prior to 3.1.9.
Patch / fix
- packagist thorsten/phpmyfaq 3.1.9
- thorsten thorsten/phpmyfaq 3.1.9
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/5915ed4c-5fe2-42e7-8fac-5dd0d032727c referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.3 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | thorsten/phpmyfaq | <3.1.9 |
3.1.9 |
Affected products
- thorsten thorsten/phpmyfaq
Classification
References
-
github.com
/thorsten/phpmyfaq/commit/8b47f38
web, patch, third-party-advisory
-
github.com
/thorsten/phpMyFAQ/commit/c16cc2bbe2687f75aa1204b804483091fae43cba
web
-
huntr.dev
/bounties/5915ed4c-5fe2-42e7-8fac-5dd0d032727c
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-4409
advisory
-
github.com
/thorsten/phpmyfaq
package
Sources
- CVE List CVE-2022-4409
- GitHub Advisory GHSA-wpgc-5cr5-h9gg
- NVD CVE-2022-4409
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.