# CVE-2022-32175: AdGuardHome - CSRF

> An attacker can trick an authorized user into modifying or deleting custom filtering rules in AdGuard Home via a malicious link.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Oct 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-mwwc-3jv2-62j3

## What is CVE-2022-32175?

CVE-2022-32175 is a medium-severity vulnerability in AdguardHome, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In AdGuardHome, versions v0.95 through v0.108.0-b.13 are vulnerable to Cross-Site Request Forgery (CSRF), in the custom filtering rules functionality. An attacker can persuade an authorized user to follow a malicious link, resulting in deleting/modifying the custom filtering rules.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-32175?

2 open source packages ship an affected version, including github.com/AdguardTeam/AdGuardHome. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/AdguardTeam/AdGuardHome` | Go | From 0.95 | 0.108.0-b.16 |
| `github.com/AdguardTeam/AdGuardHome` | Go | From 0.95 | 0.108.0-b.16 |

Products: Adguard Adguardhome.

## How do I fix CVE-2022-32175?

Upgrade github.com/AdguardTeam/AdGuardHome to 0.108.0-b.16 or later.

## Is CVE-2022-32175 being exploited?

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

## Other vulnerabilities in AdguardHome

- [CVE-2026-32136](https://insights.sbomify.com/CVE-2026-32136/): AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass (critical 9.8)
- [CVE-2026-47703](https://insights.sbomify.com/CVE-2026-47703/): AdGuard Home: DoQ-to-UDP State Reduction and Source-Port Oracle (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-32175 and fix it if it is affected.

What it is: CVE-2022-32175 is a medium-severity vulnerability in AdguardHome, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-32175 exists.

Affected packages and fixed versions:
- github.com/AdguardTeam/AdGuardHome (Go): affected from 0.95; fixed in 0.108.0-b.16
- github.com/AdguardTeam/AdGuardHome (Go): affected from 0.95; fixed in 0.108.0-b.16

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-2022-32175/ (Markdown: https://insights.sbomify.com/CVE-2022-32175/index.md)
```

## Sources

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

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