dbcve.org
Anon Proxy ServerApplication · Anonproxyserver

CVE-2025-41356

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Reflected 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 '/diagconnect.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 confidence

Reflected XSS vulnerability in Anon Proxy Server v0.104 allows attackers to inject malicious JavaScript via the 'host' parameter in the /diagconnect.php endpoint. When victims click a crafted URL, the embedded script executes in their browser, enabling session cookie theft or unauthorized actions.

MitigationImplement proper input validation and output encoding for the 'host' parameter in /diagconnect.php to neutralize script injection; consider using a whitelist approach for allowed characters.

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
Anon Proxy ServerApplication
Affected:= 0.104

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Anon Proxy Server is installed
    Locate the Anon Proxy Server installation by checking web server document roots, common application directories, or by searching for the file 'diagconnect.php'. On Linux systems, check /var/www/html/ or /opt/; on Windows, check inetpub or the application installation directory.
    Affected if The application directory contains files from Anon Proxy Server, specifically diagconnect.php at the expected path.
  2. Verify the installed version is 0.104
    Check for version information in the application. Look for a version file, check the application dashboard or admin interface for the version number, or examine the main application files for a version string.
    Affected if The installed version is exactly 0.104 - no other version is listed as affected.
  3. Confirm the vulnerable endpoint exists
    Verify that /diagconnect.php is present in the web accessible directory. Attempt to access the endpoint via HTTP GET request, for example: http://your-server/diagconnect.php
    Affected if The endpoint returns a valid HTTP response (200 OK) rather than a 404 error, indicating diagconnect.php exists.
  4. Test for unvalidated 'host' parameter reflection
    Send a crafted request to /diagconnect.php with a test payload in the 'host' parameter, for example: GET /diagconnect.php?host=<script>alert('XSS')</script>. Inspect the response to see if the script tags are returned unchanged in the HTML output without encoding or sanitization.
    Affected if The response contains the raw <script> tags or other JavaScript elements from the input parameter without HTML entity encoding (e.g., &lt;script&gt; would indicate encoding, but <script> would not).

You are affected if Anon Proxy Server version 0.104 is installed and the /diagconnect.php endpoint reflects the 'host' parameter input without HTML encoding, allowing script injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for the 'host' parameter in /diagconnect.php to neutralize script injection; consider using a whitelist approach for allowed characters.

Fix this in Anon Proxy Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41356 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41356 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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