CVE-2022-3754 json
Weak Password Requirements in thorsten/phpmyfaq
published 4y ago modified 4mo ago also GHSA-2rr3-rv49-p42f , EUVD-2022-6994
- cvss
- 7.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.8.
Patch / fix
- packagist thorsten/phpmyfaq 3.1.8
- thorsten thorsten/phpmyfaq 3.1.8
Is CVE-2022-3754 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.58% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/f4711d7f-1368-48ab-9bef-45f32e356c47 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| 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.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | thorsten/phpmyfaq | <3.1.8 |
3.1.8 |
Affected products
- thorsten thorsten/phpmyfaq
Classification
- Weakness
-
- CWE-521 Weak Password Requirements
References
-
github.com
/thorsten/phpmyfaq/commit/d7a87d2646287828c70401ca8976ef531fbc77ea
web, patch, third-party-advisory
-
huntr.dev
/bounties/f4711d7f-1368-48ab-9bef-45f32e356c47
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-3754
advisory
-
github.com
/thorsten/phpmyfaq
package
Sources
- CVE List CVE-2022-3754
- GitHub Advisory GHSA-2rr3-rv49-p42f
- NVD CVE-2022-3754
Fencer Intel 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.