VulnerabilityPublished 23 Jun 2025

CVE-2025-6509: seaswalker spring-analysis · Cross-site Scripting

Affects seaswalker spring-analysisSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately review and sanitize all user inputs, especially the 'Name' parameter in the affected function, using robust encoding libraries that prevent script injection. 2) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 3) Conduct thorough code audits focusing on input handling in the spring-analysis application to identify and remediate similar injection points. 4) Monitor web application logs for suspicious input patterns or anomalous user behavior indicative of exploitation attempts. 6) Educate users about phishing risks and encourage cautious interaction with links or inputs related to the application. 7) Employ web application firewalls (WAFs) with rules tailored to detect and block common XSS payloads targeting the spring-analysis endpoints. These steps go beyond generic advice by focusing on the specific vulnerable parameter, leveraging layered defenses, and addressing the unique challenges posed by the rolling release model.

Description

A vulnerability was found in seaswalker spring-analysis up to 4379cce848af96997a9d7ef91d594aa129be8d71. It has been declared as problematic. Affected by this vulnerability is the function echo of the file /src/main/java/controller/SimpleController.java. The manipulation of the argument Name leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

Impact

For European organizations using seaswalker spring-analysis, this vulnerability poses a moderate risk. XSS attacks can compromise user trust, lead to credential theft, and facilitate further attacks such as privilege escalation or data manipulation. Organizations in sectors with high reliance on web-based analytics or monitoring tools may face reputational damage and regulatory scrutiny, especially under GDPR if personal data is exposed or mishandled due to exploitation. The rolling release nature of the product may delay patch deployment or complicate version management, increasing exposure time. Additionally, since the vulnerability requires user interaction, phishing or social engineering campaigns could be used to lure users into triggering the exploit. The impact is particularly relevant for organizations with public-facing dashboards or internal tools accessible by multiple users, where malicious scripts could propagate or steal sensitive information.

Summary

CVE-2025-6509 is a cross-site scripting (XSS) vulnerability identified in the seaswalker spring-analysis product, specifically affecting the function 'echo' within the file /src/main/java/controller/SimpleController.java. The vulnerability arises from improper sanitization or validation of the 'Name' argument, which an attacker can manipulate to inject malicious scripts. This flaw allows remote attackers to execute arbitrary JavaScript in the context of the victim's browser when they visit a crafted URL or interact with the vulnerable application. The product follows a rolling release model, which complicates precise version tracking, but the affected commit hash is 4379cce848af96997a9d7ef91d594aa129be8d71. The vulnerability has been publicly disclosed, though no known exploits have been observed in the wild to date. According to the CVSS 4.0 vector, the vulnerability is remotely exploitable without authentication (AV:N, PR:L), requires low attack complexity (AC:L), and user interaction (UI:P). The impact on confidentiality is none, integrity is low, and availability is none, resulting in an overall medium severity with a CVSS score of 5.1. The vulnerability primarily threatens the integrity of user sessions and data by enabling script injection, which can lead to session hijacking, phishing, or defacement attacks if exploited successfully.

References

Community reviews

Loading reviews…