# CVE-2021-3172: Denial of service in n/a

> Authenticated attackers can cause a Distributed Denial of Service in Php-Fusion via the Polling feature.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-c8m3-g5j7-r8pw

## What is CVE-2021-3172?

CVE-2021-3172 is a high-severity denial of service vulnerability in n/a, published on 17 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in Php-Fusion v9.03.90 fixed in v9.10.00 allows authenticated attackers to cause a Distributed Denial of Service via the Polling feature.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2021-3172?

It affects 1 product.


Products: Php-Fusion Php-Fusion.

## How do I fix CVE-2021-3172?

No fix has been published for CVE-2021-3172 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-3172 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3172 exists.

## Other vulnerabilities in n/a

- [CVE-2010-4931](https://insights.sbomify.com/CVE-2010-4931/): Path traversal in n/a (critical 10.0)
- [CVE-2020-24949](https://insights.sbomify.com/CVE-2020-24949/): Command injection in n/a (high 8.8)
- [CVE-2020-12461](https://insights.sbomify.com/CVE-2020-12461/): SQL injection in n/a (high 8.8)
- [CVE-2019-12099](https://insights.sbomify.com/CVE-2019-12099/): File upload in n/a (high 8.8)
- [CVE-2014-8596](https://insights.sbomify.com/CVE-2014-8596/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3172 and fix it if it is affected.

What it is: CVE-2021-3172 is a high-severity denial of service vulnerability in n/a, published on 17 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3172 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-3172/ (Markdown: https://insights.sbomify.com/CVE-2021-3172/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-3172
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-3172
- OSV: https://osv.dev/vulnerability/CVE-2021-3172

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-3172/
Summaries are generated and may contain mistakes; the official description above is the record.