CVE-2022-3721 | Code Injection in froxlor/froxlor

Code Injection in GitHub repository froxlor/froxlor prior to 0.10.39.

Published: 2022-11-04 Last update: 2025-05-02 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-3721 is rated Low Risk (39.4/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.39%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-3721

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-17 0.16% 0.39% +0.23%
2 2026-01-30 0.14% 0.16% +0.02%
3 2025-11-21 — 0.14% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-3721

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.6 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.1 2.5 [email protected]
7.6 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.8 4.7 [email protected]

Weakness enumeration for CVE-2022-3721

GitHub Security Advisory for CVE-2022-3721

GHSA-h95w-p3x6-wwj6 · Severity: medium · Ecosystem: composer — Froxlor vulnerable to Code Injection

Affected software / configurations for CVE-2022-3721

Vendor Product Version Raw CPE
froxlor froxlor < 0.10.39 cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:*

References for CVE-2022-3721

cvelogic Threat Intelligence