CVE-2023-5865 Insufficient Session Expiration in thorsten/phpmyfaq
High 7.6
Published
Updated
Check this codebase for CVE-2023-5865 and fix it if it is affected.
What it is: CVE-2023-5865 is a high-severity vulnerability in Phpmyfaq Phpmyfaq, published on 31 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5865 exists.
Affected packages and fixed versions:
- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 3.2.2
- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 3.2.2
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2023-5865/ (Markdown: https://insights.sbomify.com/CVE-2023-5865/index.md)
Attackers can hijack user sessions due to insufficient expiration, allowing unauthorized access to accounts in phpMyFAQ.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-5865?
CVE-2023-5865 is a high-severity vulnerability in Phpmyfaq Phpmyfaq, published on 31 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Insufficient Session Expiration in GitHub repository thorsten/phpmyfaq prior to 3.2.2.
Weakness: CWE-613
Which versions are affected by CVE-2023-5865?
2 open source packages ship an affected version, including thorsten/phpmyfaq. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
thorsten/phpmyfaq Packagist | All versions | 3.2.2 |
thorsten/phpmyfaq Packagist | All versions | 3.2.2 |
Products include Phpmyfaq Phpmyfaq.
How do I fix CVE-2023-5865?
Upgrade thorsten/phpmyfaq to 3.2.2 or later.
Is CVE-2023-5865 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5865 exists.
Other vulnerabilities in Phpmyfaq Phpmyfaq
- CVE-2023-0310 Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq
- CVE-2022-4407 Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq
- CVE-2017-11187 Security feature bypass in n/a
- CVE-2026-76213 phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle
- CVE-2026-76214 phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge
Sources
Also known as GHSA-f728-prhw-2g68.