Description
phpMyFAQ prior to version 3.1.8 has Weak Password Requirements. Version 3.1.8 introduces an eight-character minimum password length.
Basic information
- Type
- reviewed
- Severity
- critical
- Advisory on GitHub
- Open advisory ↗
- Repository advisory
- —
- Source code
- Browse source ↗
- Published (advisory)
- 2022-10-29 19:00:27 UTC
- Updated
- 2023-01-30 05:03:21 UTC
- GitHub reviewed
- 2022-10-31 19:26:27 UTC
- NVD published
- 2022-10-29
EPSS Score
| Score |
Percentile |
|
0.87%
|
75.03% |
CVSS Scores
| Base score |
Version |
Severity |
Vector |
|
9.8
|
3.1 |
—
|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Click to expand
- Attack vector (AV:N)
- Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
- Attack complexity (AC:L)
- Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
- Privileges required (PR:N)
- No account or special rights needed—anonymous or random user is enough.
- User interaction (UI:N)
- Nobody has to click “OK” or open a trap file; it can work without a victim helping.
- Scope (S:U)
- Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
- Confidentiality (C:H)
- Serious risk that confidential data gets exposed in a big way.
- Integrity (I:H)
- They could widely tamper with or forge data—trust in the data is badly hurt.
- Availability (A:H)
- Could take the service down hard or make it unusable for people who depend on it.
|
CWEs
| CWE id |
Name |
|
CWE-521
|
Weak Password Requirements |
Affected packages (1)
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem |
Package |
Vulnerable range |
First patched |
Vulnerable functions |
| composer |
thorsten/phpmyfaq |
< 3.1.8 |
3.1.8 |
—
|
cvelogic
Threat Intelligence