LiveActive security incident?Get immediate response
CVE Record

CVE-2025-60302: code-projects Client Details System 1.0 is vulnerable to Cross Site Scripting (XSS).

code-projects Client Details System 1.0 is vulnerable to Cross Site Scripting (XSS). When adding customer information, the client details system fills in malicious JavaScript code in the username field.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE describes a medium-severity cross-site scripting issue in code-projects Client Details System 1.0. Malicious script can be stored or entered through the username field when adding customer information, potentially affecting users who later view that data.

Executive priority

Address on a normal vulnerability-management timeline unless the application is internet-facing or used by privileged staff. Prioritize confirming whether this niche product is actually present, because source metadata is incomplete.

Technical view

The issue is CWE-79 XSS with CVSS 3.1 score 6.1. The vector indicates network reachability, low attack complexity, no privileges required, required user interaction, changed scope, and low confidentiality and integrity impact. The source bundle does not identify a vendor patch.

Likely exposure

Exposure appears limited to deployments of code-projects Client Details System 1.0. The CVE affected-product fields are listed as n/a, so teams should verify the application name and version from deployed assets rather than relying only on inventory matching.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The described flaw requires a victim interaction, such as viewing affected customer data containing script content.

Researcher notes

Evidence is sparse: the CVE names code-projects Client Details System 1.0 and a username-field XSS, but the structured affected fields are n/a. Avoid broad product assumptions and validate directly against the referenced application and version.

Mitigation direction

  • Check the project or vendor reference for patch guidance before changing production.
  • Restrict access to the customer-entry and customer-viewing pages where feasible.
  • Treat username values as untrusted in any maintained fork.
  • Apply output encoding and input validation if responsible for the application code.
  • Review stored customer records for suspicious script-like content.

Validation and detection

  • Confirm whether Client Details System 1.0 is deployed anywhere.
  • Inspect the add-customer workflow and username handling path.
  • Review rendered customer views for unencoded username output.
  • Check logs or records for suspicious username entries.
  • Document whether a vendor fix or local code control is applied.
Prepared
Confidence
medium
Sources
3

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-60302 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2025-60302Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.