VulnerabilityPublished 2 Dec 2025

CVE-2025-65215: Cross-site Scripting

Source CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 09:15 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 13% 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 2 Dec 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 CVE-2025-65215, organizations should implement strict input validation and output encoding on the Supplier Name field to neutralize malicious scripts. Employing context-aware encoding (e.g., HTML entity encoding) before rendering user input in the web interface is critical. Deploy Web Application Firewalls (WAFs) configured to detect and block XSS payloads targeting the affected endpoint. Conduct regular security assessments and code reviews focusing on user input handling in the application. Educate users about phishing risks to reduce the chance of successful social engineering attacks that could trigger the vulnerability. Monitor web server and application logs for unusual requests or script injection attempts. Coordinate with the vendor or development team to obtain patches or updates addressing this vulnerability as soon as they become available. If patching is delayed, consider isolating or restricting access to the vulnerable module to trusted users only. Additionally, implement Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers.

Description

CVE-2025-65215 is a medium severity Cross Site Scripting (XSS) vulnerability in Sourcecodester Web-based Pharmacy Product Management System v1.0, specifically in the Supplier Name field of the /product_expiry/add-supplier.php page. The vulnerability allows unauthenticated remote attackers to inject malicious scripts that execute in the context of other users, potentially leading to session hijacking or data manipulation. Exploitation requires user interaction but no prior authentication. Although no known exploits are reported in the wild, the vulnerability impacts confidentiality and integrity with a CVSS score of 6.1. European organizations using this system, especially pharmacies and healthcare providers, could face targeted attacks compromising sensitive data. Mitigation involves implementing proper input validation and output encoding on the Supplier Name field, deploying Web Application Firewalls (WAFs) with XSS filtering, and monitoring logs for suspicious activity. Countries with significant healthcare IT adoption and use of Sourcecodester products, such as Germany, France, and the UK, are most likely to be affected.

Impact

For European organizations, particularly those in the healthcare and pharmaceutical sectors using the Sourcecodester Pharmacy Product Management System, this vulnerability poses a risk to the confidentiality and integrity of supplier and product data. Attackers could exploit the XSS flaw to hijack user sessions, steal sensitive information, or inject malicious scripts that alter displayed data, potentially disrupting inventory management or expiry tracking. This could lead to operational inefficiencies, regulatory compliance issues, and reputational damage. Although availability is not directly impacted, the indirect effects of data manipulation could affect patient safety and supply chain reliability. The vulnerability’s requirement for user interaction means phishing or social engineering could be used to lure users into triggering the exploit. European healthcare providers are subject to strict data protection regulations (e.g., GDPR), so exploitation could also result in legal and financial penalties. The absence of known active exploits provides a window for proactive mitigation, but the medium severity and scope change indicate a meaningful risk that should not be ignored.

Summary

CVE-2025-65215 identifies a Cross Site Scripting (XSS) vulnerability in the Sourcecodester Web-based Pharmacy Product Management System version 1.0. The flaw exists in the Supplier Name input field on the /product_expiry/add-supplier.php page, where user-supplied input is not properly sanitized or encoded before being reflected in the web application’s output. This allows an attacker to inject malicious JavaScript code that executes in the browsers of users who view the affected page, potentially leading to session hijacking, theft of cookies, or manipulation of displayed data. The vulnerability is remotely exploitable over the network without requiring authentication, but it does require user interaction (e.g., a user visiting a crafted URL or page). The CVSS 3.1 base score of 6.1 reflects a medium severity, with network attack vector, low attack complexity, no privileges required, but user interaction needed. The scope is changed (S:C), indicating the vulnerability can affect resources beyond the vulnerable component. The confidentiality and integrity impacts are low, while availability is not affected. No known exploits have been reported in the wild as of the publication date. The vulnerability is classified under CWE-79, a common and well-understood web application security issue. Given the nature of the affected system—a pharmacy product management platform—successful exploitation could lead to unauthorized access to supplier information or manipulation of product expiry data, which could indirectly impact operational integrity and patient safety.

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

Description

AI analysisMachine-generated, updated 9 Dec 2025, 19:11 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats