How severe is CVE-2021-42325?

CVE-2021-42325 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-42325?

CVE-2021-42325 affects the following packages: froxlor/froxlor (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2021-42325?

Update froxlor/froxlor to 0.10.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-42325 is resolved across your whole dependency graph.

How do I detect CVE-2021-42325 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for froxlor/froxlor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-42325 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2021-42325 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2021-42325, including 1 documented proof-of-concept exploit on Exploit-DB and 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 CVE-2021-42325?

CVE-2021-42325 has an EPSS (Exploit Prediction Scoring System) score of 11.8%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2021-42325?

CVE-2021-42325 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 CVE-2021-42325 published, and has it been updated?

CVE-2021-42325 was published on October 12, 2021 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2021-42325 — froxlor

CRITICALFix: Froxlor/Froxlor@eb59234

CVE-2021-42325 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in froxlor/froxlor. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for froxlor/froxlor — see the affected versions and patch details below.

Froxlor SQL injection vulnerability

Also known asGHSA-6fvw-x6gw-4wv8

Published

Oct 12, 2021

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

11.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘froxlor/froxlor

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

Froxlor through 0.10.29.1 allows SQL injection in Database/Manager/DbManagerMySQL.php via a custom DB name.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`froxlor/froxlor`	all versions	0.10.30`composer require froxlor/froxlor:^0.10.30`

Affected Products

1 product · 1 configurations

Application

froxlorfroxlor

< 0.10.30

range

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.

EDB-50502webappsphp

Froxlor 0.10.29.1 - SQL Injection (Authenticated)

by Martin Cernac · Nov 8, 2021

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for froxlor/froxlor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update froxlor/froxlor to 0.10.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-42325 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

Froxlor through 0.10.29.1 allows SQL injection in Database/Manager/DbManagerMySQL.php via a custom DB name.

O3 Security · Impact-Aware SCA

Is CVE-2021-42325 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template or Metasploit module yet. 2 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

Froxlor

3.5/10

Code-Review0/10

Maintained10/10

Branch-ProtectionN/A

Assessed Nov 9, 2026

Timeline

Disclosed

Oct 12, 2021

First exploit

Nov 8, 2021

Last updated

Oct 20, 2026

Identifiers

CVE-2021-42325

GHSA-6fvw-x6gw-4wv8

References

Advisorypacketstormsecurity.com · Froxlor 0.10.29.1 SQL Injection Advisoryexploit-db.com Advisorynvd.nist.gov · CVE 2021 42325 Fixgithub.com · eb592340b022298f62a0a3e8450dbfbe29585782 Packagegithub.com · Froxlor

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs affecting froxlor/froxlor is rated as high or higher (top: critical).

CVE-2026-54347CVE-2026-54543CVE-2026-62988CVE-2026-54348CVE-2026-55593GHSA-mr9h-45p9-fg8hGHSA-q4rm-m6xh-5pv7CVE-2026-41234

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2021-42325 — froxlor

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-42325 in your dependencies?