CVE-2025-65368VulnerabilityPublished 15 Jan 2026

CVE-2025-65368: SparkyFitness · n/a

Affects SparkyFitnessSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.1Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jan 2026
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 2026-10-25.

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

Affected software

Product	Affected	Fixed in
GitHubcodewithcj/SparkyFitness`pkg:github/codewithcj/SparkyFitness`Other threats	Affected =0.15.8.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-65368, organizations should implement strict input validation and output encoding on all user-supplied data and AI-generated content before rendering it in the browser. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. Monitor application logs and user behavior for signs of exploitation attempts, such as unusual script injections or anomalous user interactions. Until an official patch is released, consider disabling or restricting features that incorporate LLM-generated outputs if feasible. Conduct security testing focused on AI-generated content to identify and remediate similar vulnerabilities proactively. Educate users about the risks of interacting with untrusted links or content within the application. Collaborate with the SparkyFitness vendor to obtain timely updates and apply patches promptly once available. Additionally, review and enhance web application firewalls (WAFs) rules to detect and block XSS payloads targeting this vulnerability. For organizations with compliance obligations, document mitigation efforts and risk assessments to demonstrate due diligence.

Description

CVE-2025-65368 is a medium severity Cross Site Scripting (XSS) vulnerability affecting SparkyFitness version 0.15.8.2. The flaw arises from improper sanitization of user input and outputs generated by large language models (LLMs), allowing attackers to inject malicious scripts. Exploitation requires user interaction but no authentication, and can lead to partial compromise of confidentiality and integrity, though availability is not impacted. This vulnerability has a CVSS score of 6.1, reflecting its moderate risk level. No known exploits are currently reported in the wild, and no patches have been published yet. European organizations using SparkyFitness, especially those in countries with high adoption of fitness and wellness software, should be vigilant.

Impact

For European organizations, the impact of CVE-2025-65368 could be significant in sectors relying on SparkyFitness for employee wellness programs or customer engagement. Successful exploitation could lead to unauthorized disclosure of personal data, including health-related information, violating GDPR and other privacy regulations. The partial compromise of data integrity could result in manipulated fitness data, affecting decision-making or user trust. Although availability is not impacted, the reputational damage and potential regulatory penalties could be substantial. Organizations with large user bases are at higher risk due to the increased likelihood of user interaction with malicious content. The involvement of LLM outputs in the vulnerability also highlights risks in AI-driven features, which are increasingly adopted in European digital services. Attackers could leverage this vulnerability to conduct phishing campaigns or deliver further malware via injected scripts. The lack of available patches means organizations must rely on interim mitigations, increasing operational complexity. Overall, the threat underscores the need for rigorous security controls around AI integrations and user input handling in web applications.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jan 2026, 21:35 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats