Security readout for executives and security teams
Plain-English summary
A flaw in code-projects Blood System 1.0 may let an attacker place malicious browser content in the city field processed by /don.php. A user must interact with affected content. Successful abuse could expose limited browser-accessible information or alter displayed content, but the CVSS assessment indicates no availability impact.
Executive priority
Treat this as a moderate, prompt-remediation issue for exposed deployments rather than an emergency. Prioritize internet-facing or sensitive installations because exploitation requires no authentication, although user interaction is required. Escalate priority if internal testing confirms unsafe rendering or if credible exploitation evidence emerges.
Technical view
CVE-2025-65342 is a CWE-79 cross-site scripting vulnerability involving the city field at /don.php. CVSS 3.1 scores it 6.1: network reachable, low complexity, no privileges required, user interaction required, changed scope, low confidentiality and integrity impact, and no availability impact. The supplied evidence does not classify the XSS as stored, reflected, or DOM-based.
Likely exposure
Deployments of code-projects Blood System 1.0 exposing /don.php are the likely concern, especially internet-facing systems. However, the structured affected-product data says “n/a,” conflicting with the title and description. Confirm product identity, version, route availability, and whether untrusted city values reach browser output.
Exploitation context
The supplied record is not listed in CISA KEV, and no cited source establishes active exploitation. Exploitation requires user interaction according to the CVSS vector. This absence of evidence should not be interpreted as proof that exploitation has never occurred.
Researcher notes
Evidence identifies the parameter and endpoint but does not establish the XSS subtype, persistence, exact browser context, authentication state of affected viewers, or an official fix. The product/version statement conflicts with structured affected metadata. Reproduce only in an authorized environment and avoid assuming broader affected versions.
Mitigation direction
Check project or vendor guidance for an official correction; no patch is identified in the supplied sources.
Restrict public access to /don.php when operationally unnecessary.
Apply context-aware output encoding before rendering city values in browser content.
Validate and sanitize untrusted city input as defense in depth.
Consider temporarily disabling affected donation functionality if exposure cannot be safely controlled.
Validation and detection
Inventory Blood System deployments and confirm whether version 1.0 is present.
Determine whether /don.php is reachable from untrusted networks.
Trace the city field from request handling to every browser-rendering context.
Use authorized, non-destructive testing to confirm that city input is safely encoded.
Verify remediation prevents script interpretation without breaking legitimate city values.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.