Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11291: Cross Site Scripting in ixmaps website2017

0
Medium
VulnerabilityCVE-2025-11291cvecve-2025-11291
Published: Sun Oct 05 2025 (10/05/2025, 13:32:05 UTC)
Source: CVE Database V5
Vendor/Project: ixmaps
Product: website2017

Description

A security flaw has been discovered in ixmaps website2017 up to 0c71cffa0162186bc057a76766bc97e9f5a3a2d0. This impacts an unknown function of the file /map.php of the component HTTP GET Request Handler. Performing manipulation of the argument trid results in cross site scripting. The attack can be initiated remotely. The exploit has been released to the public and may be exploited. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 10/12/2025, 13:47:58 UTC

Technical Analysis

CVE-2025-11291 identifies a cross-site scripting (XSS) vulnerability in the ixmaps website2017 product, affecting versions up to commit 0c71cffa0162186bc057a76766bc97e9f5a3a2d0. The vulnerability is located in the /map.php file within the HTTP GET Request Handler component, specifically through manipulation of the 'trid' argument. This parameter is not properly sanitized, allowing an attacker to inject malicious JavaScript code that executes in the context of the victim's browser. The attack vector is remote and does not require authentication, but user interaction is necessary, typically by convincing a user to click a crafted URL containing the malicious 'trid' parameter. The vulnerability has a CVSS 4.0 score of 5.3, indicating medium severity, with an exploit publicly available. The vendor uses continuous delivery with rolling releases, complicating identification of affected versions and patch availability. Despite early notification, the vendor has not responded or issued a fix. The vulnerability can be exploited to steal session cookies, perform actions on behalf of the user, or redirect users to malicious sites, undermining confidentiality and integrity of user data. The lack of vendor response and public exploit availability increases the urgency for organizations to implement mitigations independently.

Potential Impact

For European organizations, this XSS vulnerability poses risks primarily to confidentiality and integrity of user sessions and data. Exploitation can lead to session hijacking, unauthorized actions, phishing, and malware distribution. Organizations relying on ixmaps website2017 for geospatial or mapping services may experience reputational damage and loss of user trust if exploited. The vulnerability's remote exploitability without authentication broadens the attack surface, especially for public-facing web applications. Given the vendor's lack of response, organizations must assume prolonged exposure. Potential impacts include data leakage, unauthorized access to sensitive information, and disruption of service trustworthiness. Sectors such as government, transportation, urban planning, and research institutions using ixmaps in Europe are particularly vulnerable. The medium severity rating suggests moderate but non-trivial risk, warranting prompt mitigation to prevent exploitation and downstream impacts.

Mitigation Recommendations

1. Implement strict input validation and output encoding on the 'trid' parameter in /map.php to neutralize malicious scripts. 2. Deploy a Web Application Firewall (WAF) with custom rules to detect and block XSS payloads targeting the 'trid' parameter. 3. Employ Content Security Policy (CSP) headers to restrict script execution sources and mitigate impact of injected scripts. 4. Conduct user awareness training to recognize suspicious links and avoid clicking untrusted URLs. 5. Monitor web server logs for unusual requests containing suspicious 'trid' parameter values indicative of exploitation attempts. 6. If feasible, isolate or sandbox the affected web application to limit potential damage. 7. Engage with the vendor or community to track any forthcoming patches or updates. 8. Consider alternative mapping solutions if mitigation is not possible or vendor support remains absent. 9. Regularly update all related software components and dependencies to reduce attack surface. 10. Test mitigations in a staging environment before deployment to ensure no disruption to legitimate functionality.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-10-04T18:36:39.599Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68e274eea08882725d27c484

Added to database: 10/5/2025, 1:38:54 PM

Last enriched: 10/12/2025, 1:47:58 PM

Last updated: 11/22/2025, 5:32:11 PM

Views: 50

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats