How severe is CVE-2022-3552?

CVE-2022-3552 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-3552 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 44% (99th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-3552?

CVE-2022-3552 affects Boxbilling. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-3552?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-3552 published?

CVE-2022-3552 was published on 2022-10-17 and last updated on 2026-06-17.

CVE-2022-3552

CVE-2022-3552 is a high-severity vulnerability in Boxbilling with a CVSS 3.x base score of 7.2. Its EPSS exploit-prediction score of 44% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-434.

Key facts

Severity: High (CVSS 3.x base score 7.2)
EPSS exploit prediction: 44% (99th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-434
Affected product: Boxbilling
Published: 2022-10-17
Last modified: 2026-06-17

Description

Unrestricted Upload of File with Dangerous Type in GitHub repository boxbilling/boxbilling prior to 0.0.1.

Frequently asked questions

What is CVE-2022-3552?: Unrestricted Upload of File with Dangerous Type in GitHub repository boxbilling/boxbilling prior to 0.0.1.
How severe is CVE-2022-3552?: CVE-2022-3552 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-3552 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 44% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-3552?: CVE-2022-3552 affects Boxbilling. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-3552?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-3552 published?: CVE-2022-3552 was published on 2022-10-17 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:boxbilling:boxbilling:*:*:*:*:*:*:*:*

More vulnerabilities in Boxbilling

CVE-2020-23647 — Medium (CVSS 6.1): Cross Site Scripting (XSS) vulnerability in BoxBilling 4.19, 4.19.1, 4.20, and 4.21 allows remote attackers to run…

All CVEs affecting Boxbilling →

Other CWE-434 (Unrestricted Upload of File with Dangerous Type) vulnerabilities

CVE-2026-56291 — Critical (CVSS 10.0): The Joomla extension Balbooa Forms is vulnerable to an unauthenticated arbitrary file upload that allows uploading…
CVE-2026-48283 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Unrestricted Upload of File with Dangerous Type…
CVE-2026-48276 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Unrestricted Upload of File with Dangerous Type…
CVE-2026-57700 — Critical (CVSS 10.0): Unrestricted Upload of File with Dangerous Type vulnerability in Daan.Dev OMGF Pro allows Using Malicious Files. This…
CVE-2025-69129 — Critical (CVSS 10.0): Unauthenticated Arbitrary File Upload in WordPress & WooCommerce Scraper Plugin, Import Data from Any Site <= 1.0.7…
CVE-2026-40772 — Critical (CVSS 10.0): Unauthenticated Arbitrary File Upload in GeekyBot <= 1.2.2 versions.

Browse all CWE-434 (Unrestricted Upload of File with Dangerous Type) vulnerabilities →