How severe is GHSA-f9c6-4j9h-6c5r?

GHSA-f9c6-4j9h-6c5r has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-f9c6-4j9h-6c5r?

GHSA-f9c6-4j9h-6c5r affects the following packages: thorsten/phpmyfaq (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-f9c6-4j9h-6c5r?

Update thorsten/phpmyfaq to 3.1.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9c6-4j9h-6c5r is resolved across your whole dependency graph.

How do I detect GHSA-f9c6-4j9h-6c5r in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thorsten/phpmyfaq. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-f9c6-4j9h-6c5r if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-f9c6-4j9h-6c5r?

O3 pinpoints whether GHSA-f9c6-4j9h-6c5r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-f9c6-4j9h-6c5r actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-f9c6-4j9h-6c5r, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-f9c6-4j9h-6c5r?

GHSA-f9c6-4j9h-6c5r is classified as CWE-115 (CWE-115). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f9c6-4j9h-6c5r published, and has it been updated?

GHSA-f9c6-4j9h-6c5r was published on February 17, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-f9c6-4j9h-6c5r

MEDIUM

GHSA-f9c6-4j9h-6c5r is a medium-severity (CVSS 4.3) CWE-115 vulnerability in thorsten/phpmyfaq. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-f9c6-4j9h-6c5r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Misinterpretation of Input in thorsten/phpmyfaq

Also known asCVE-2023-0880

Published

Feb 17, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

🐘thorsten/phpmyfaq

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Misinterpretation of Input in GitHub repository thorsten/phpmyfaq prior to 3.1.11.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`thorsten/phpmyfaq`	all versions	3.1.11

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Misinterpretation of Input in GitHub repository thorsten/phpmyfaq prior …

huntr.devNVDFeb 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thorsten/phpmyfaq. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update thorsten/phpmyfaq to 3.1.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9c6-4j9h-6c5r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-f9c6-4j9h-6c5r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f9c6-4j9h-6c5r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Misinterpretation of Input in GitHub repository thorsten/phpmyfaq prior to 3.1.11.

O3 Security · Impact-Aware SCA

Is GHSA-f9c6-4j9h-6c5r in your dependencies?

O3 detects GHSA-f9c6-4j9h-6c5r across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works