How severe is GHSA-84gf-rw24-pfqg?

GHSA-84gf-rw24-pfqg has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-84gf-rw24-pfqg?

GHSA-84gf-rw24-pfqg affects the following packages: nukeviet/nukeviet (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-84gf-rw24-pfqg?

Update nukeviet/nukeviet to 4.3.08 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84gf-rw24-pfqg is resolved across your whole dependency graph.

How do I detect GHSA-84gf-rw24-pfqg in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nukeviet/nukeviet. 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-84gf-rw24-pfqg 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-84gf-rw24-pfqg?

O3 pinpoints whether GHSA-84gf-rw24-pfqg 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-84gf-rw24-pfqg actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-84gf-rw24-pfqg, 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 is the EPSS score for GHSA-84gf-rw24-pfqg?

GHSA-84gf-rw24-pfqg has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 72th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-84gf-rw24-pfqg?

GHSA-84gf-rw24-pfqg is classified as SQL Injection (CWE-89). 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-84gf-rw24-pfqg published, and has it been updated?

GHSA-84gf-rw24-pfqg was published on May 24, 2022 and was last updated on April 24, 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-84gf-rw24-pfqg

CRITICAL

NukeViet SQL Injection vulnerability via topicsid parameter

Also known asCVE-2020-21808

Published

May 24, 2022

Updated

Apr 24, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk72th percentile+1.01%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐘nukeviet/nukeviet

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

SQL Injection vulnerability in NukeViet CMS 4.0.10 - 4.3.07 via the topicsid parameter in modules/news/admin/addtotopics.php.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`nukeviet/nukeviet`	≥ 4.0.10&&< 4.3.08	4.3.08

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.

SQL Injection vulnerability in NukeViet CMS 4.0.10 - 4.3.07 via:the topi…

whitehub.netNVDAug 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nukeviet/nukeviet. 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 nukeviet/nukeviet to 4.3.08 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84gf-rw24-pfqg 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-84gf-rw24-pfqg 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-84gf-rw24-pfqg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

SQL Injection vulnerability in NukeViet CMS 4.0.10 - 4.3.07 via the topicsid parameter in `modules/news/admin/addtotopics.php`.

O3 Security · Impact-Aware SCA

Is GHSA-84gf-rw24-pfqg in your dependencies?

O3 detects GHSA-84gf-rw24-pfqg 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