CVE-2025-69606
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 · uneditedCross-Site Scripting (XSS) vulnerability was discovered in the GSVoIP web panel version 2.0.90. The `msg` parameter in the `/painel/gateways.php/error` endpoint does not properly sanitize user-supplied input, allowing attackers to inject arbitrary JavaScript into the HTML response. A remote attacker can exploit this vulnerability by sending a crafted URL to a victim, leading to unauthorized script execution, session hijacking, phishing, or other client-side attacks.
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 GSVoIP web panel v2.0.90 where the `msg` parameter in the `/painel/gateways.php/error` endpoint reflects unsanitized user input into the HTML response, allowing arbitrary JavaScript injection via crafted URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify GSVoIP web panel installationLocate the GSVoIP installation directory or check web server logs for requests to /painel/ endpoints. Confirm the application is GSVoIP by examining login pages or admin interfaces for GSVoIP branding.Affected if The system runs GSVoIP web panel software.
-
Check GSVoIP versionInspect the version file or admin interface for the installed GSVoIP version. Common locations include version.php, about.php, or the admin dashboard footer.Affected if The installed version is v2.0.90.
-
Verify vulnerable endpoint existsCheck if the file /painel/gateways.php exists on the web server. The error handler at this path processes the 'msg' parameter.Affected if The /painel/gateways.php endpoint is accessible on the server.
-
Test msg parameter reflectionSend a crafted request to the endpoint with an innocuous test payload in the msg parameter, for example: /painel/gateways.php/error?msg=<script>alert(1)</script>. Inspect the HTTP response to see if the script tags are returned verbatim without HTML encoding.Affected if The msg parameter value is reflected in the response without being HTML-encoded or sanitized.
-
Confirm XSS execution potentialExamine the response context - whether the unsanitized input lands inside HTML tags, attributes, or JavaScript contexts where it could execute.Affected if The unsanitized msg parameter value appears in the HTML response in a way that could execute JavaScript (e.g., inside unquoted attributes, script tags, or event handlers).
A user is affected if they run GSVoIP web panel version v2.0.90 with the /painel/gateways.php endpoint accessible and the msg parameter reflecting unencoded user input in the response.
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 and output encoding/HTML escaping for the `msg` parameter before reflecting it in the response. Consider using a whitelist approach for allowed characters.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69606 — 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-69606 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