# AdGuardHome vulnerable to Cross-Site Request Forgery

Advisory record · `GHSA-mwwc-3jv2-62j3`

- **Identifiers:** `GHSA-mwwc-3jv2-62j3` · `CVE-2022-32175`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 11 Oct 2022
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 11 Oct 2022, 19:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/AdguardTeam/AdGuardHome` (Go): affected `>=0.95, <0.108.0-b.16`; fixed in `0.108.0-b.16`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> AdGuardHome versions 0.95 through 0.108.0-b.13 are vulnerable to Cross-Site Request Forgery in the custom filtering rules functionality. An attacker who persuades an authorized user to follow a malicious link can delete or modify that user's custom filtering rules. Upgrade to 0.108.0-b.16, where the vulnerable code is no longer present.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 27th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:43 UTC: First seen by agentprime
- 31 Oct 2026, 14:43 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mwwc-3jv2-62j3)

## Sources

- [GitHub Advisory Database: GHSA-mwwc-3jv2-62j3](https://github.com/advisories/GHSA-mwwc-3jv2-62j3)
- [OSV: GHSA-mwwc-3jv2-62j3](https://osv.dev/vulnerability/GHSA-mwwc-3jv2-62j3)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-32175>
- <https://github.com/AdguardTeam/AdGuardHome/commit/756b14a61de138889130c239406dae43f1f115cb>
- <https://github.com/AdguardTeam/AdGuardHome>
- <https://github.com/AdguardTeam/AdGuardHome/blob/v0.108.0-b.13/internal/home/controlfiltering.go#L265>
- <https://github.com/AdguardTeam/AdGuardHome/blob/v0.108.0-b.15/internal/home/controlfiltering.go>
- <https://github.com/AdguardTeam/AdGuardHome/blob/v0.108.0-b.16/internal/home/controlfiltering.go>
- <https://www.mend.io/vulnerability-database/CVE-2022-32175>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-mwwc-3jv2-62j3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mwwc-3jv2-62j3/>. Everything for agents: <https://agentprime.io/llms.txt>.
