GHSA-mwwc-3jv2-62j3 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in github.com/AdguardTeam/AdGuardHome. 2 public exploit references exist, so weaponization risk is real. A fix is available for github.com/AdguardTeam/AdGuardHome — see the affected versions and patch details below.
AdGuardHome vulnerable to Cross-Site Request Forgery
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-mwwc-3jv2-62j3.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-mwwc-3jv2-62j3 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/AdguardTeam/AdGuardHomeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
The file that contains the vulnerable code is no longer present as of v0.108.0-b.16.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/AdguardTeam/AdGuardHome | ≥ 0.95&&< 0.108.0-b.16 | 0.108.0-b.16go get github.com/AdguardTeam/AdGuardHome@v0.108.0-b.16 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/AdguardTeam/AdGuardHome, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/AdguardTeam/AdGuardHome to 0.108.0-b.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mwwc-3jv2-62j3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mwwc-3jv2-62j3 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mwwc-3jv2-62j3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mwwc-3jv2-62j3 in your dependencies?
O3 Security finds GHSA-mwwc-3jv2-62j3 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.