CVE-2023-2429 json
Improper Access Control in thorsten/phpmyfaq
published 2023-04-30 3 y ago modified 2026-06-17 4 mo ago also GHSA-r69v-q48g-3966 , EUVD-2023-1387
- cvss
- 6.6
- 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 45%
- public exploits
- 0
- none known
Summary
Improper Access Control in GitHub repository thorsten/phpmyfaq prior to 3.1.13.
Patch / fix
- packagist thorsten/phpmyfaq 3.1.13
- thorsten thorsten/phpmyfaq 3.1.13
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.com https://huntr.com/bounties/20d3a0b3-2693-4bf1-b196-10741201a540 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.6 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.0 | 6.6 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | thorsten/phpmyfaq | <3.1.13 |
3.1.13 |
Affected products
- thorsten thorsten/phpmyfaq
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
github.com
/thorsten/phpmyfaq/commit/07552f5577ff8b1e6f7cdefafcce9b2a744d3a24
web, patch
-
huntr.com
/bounties/20d3a0b3-2693-4bf1-b196-10741201a540
exploit, web
-
huntr.dev
/bounties/20d3a0b3-2693-4bf1-b196-10741201a540
web, permissions-required
-
nvd.nist.gov
/vuln/detail/CVE-2023-2429
advisory
-
github.com
/thorsten/phpmyfaq
package
Sources
- CVE List CVE-2023-2429
- GitHub Advisory GHSA-r69v-q48g-3966
- NVD CVE-2023-2429
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.