How severe is GHSA-94r7-63g8-c4jw?

GHSA-94r7-63g8-c4jw has a CVSS score of 6.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-94r7-63g8-c4jw?

GHSA-94r7-63g8-c4jw affects the following packages: thorsten/phpmyfaq (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-94r7-63g8-c4jw?

Update thorsten/phpmyfaq to 3.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-94r7-63g8-c4jw is resolved across your whole dependency graph.

How do I detect GHSA-94r7-63g8-c4jw 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-94r7-63g8-c4jw 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-94r7-63g8-c4jw?

O3 pinpoints whether GHSA-94r7-63g8-c4jw 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-94r7-63g8-c4jw actively exploited in the wild?

No public exploit code has been indexed for GHSA-94r7-63g8-c4jw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-94r7-63g8-c4jw?

GHSA-94r7-63g8-c4jw is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-94r7-63g8-c4jw published, and has it been updated?

GHSA-94r7-63g8-c4jw was published on May 31, 2023 and was last updated on February 16, 2024. 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-94r7-63g8-c4jw

MEDIUM

GHSA-94r7-63g8-c4jw is a medium-severity (CVSS 6.7) Cross-site Scripting (XSS) vulnerability in thorsten/phpmyfaq. O3 Security confirms whether GHSA-94r7-63g8-c4jw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

thorsten/phpmyfaq vulnerable to cross-site scripting

Also known asCVE-2023-2999

Published

May 31, 2023

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

thorsten/phpmyfaq prior to 3.1.14 is vulnerable to a stored cross-site scripting attack perpetuated by an actor logged in as admin.

Affected Packages

1 total 1 fixed

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

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.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-94r7-63g8-c4jw 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-94r7-63g8-c4jw 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-94r7-63g8-c4jw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

thorsten/phpmyfaq prior to 3.1.14 is vulnerable to a stored cross-site scripting attack perpetuated by an actor logged in as admin.

O3 Security · Impact-Aware SCA

Is GHSA-94r7-63g8-c4jw in your dependencies?

O3 detects GHSA-94r7-63g8-c4jw 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