CVE-2025-41357
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedReflected Cross-Site Scripting (XSS) vulnerability in Anon Proxy Server v0.104. This vulnerability allows an attacker to execute JavaScript code in the victim's browser by sending him/her a malicious URL. This vulnerability can be exploited to steal sensitive user data, such as session cookies, or to perform actions on behalf of the user. It affects 'host' parameter in '/diagdns.php' endpoint.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceReflected XSS vulnerability in the 'host' parameter of the /diagdns.php endpoint in Anon Proxy Server v0.104. User-supplied input in the host parameter is rendered without proper sanitization or output encoding, allowing injection of arbitrary JavaScript code that executes in victim's browser.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.104CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Anon Proxy Server versionLocate the installed Anon Proxy Server version by checking the application's about page, version file, or running 'anonproxyserver --version' or similar version command provided by the application.Affected if The installed version is exactly 0.104 (version 0.104)
-
Verify diagdns.php endpoint existsLocate the diagdns.php file in the web server's document root or application directory. Common paths may include /var/www/html/, /www/, or the application's web directory. Search for the file named 'diagdns.php'.Affected if The file diagdns.php exists in the application web directory
-
Inspect host parameter handling in source codeOpen diagdns.php in a text editor or view its source code. Locate the section that processes the 'host' parameter (typically via $_GET['host'] or $_POST['host']). Check if the value is directly echoed or rendered without HTML encoding (such as htmlspecialchars() or equivalent) or input validation.Affected if The host parameter value is output directly without htmlspecialchars(), htmlentities(), or similar encoding functions
-
Check if endpoint accepts user inputSend a request to /diagdns.php with a test value in the host parameter, for example: GET /diagdns.php?host=test. Examine the response to confirm the parameter value is reflected in the output.Affected if The host parameter value is reflected in the page response without encoding
If the installed version is 0.104 AND the diagdns.php endpoint exists AND the host parameter is processed without HTML encoding, the environment is affected by this reflected XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper input validation for the host parameter (allowlist valid hostname/IP formats) and ensure all output is HTML-encoded before rendering. Consider using security frameworks or built-in encoding functions specific to the application's language.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-41357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data