Security readout for executives and security teams
Plain-English summary
ProjectSend versions before r1053 have a cross-site scripting issue in the My Account page Name field. If reachable by users, this could let attacker-controlled script run in a user’s browser. The public record does not provide CVSS scoring, exploit details, or broad impact evidence.
Executive priority
Treat this as a targeted web-application hygiene issue, not a confirmed emergency. Prioritize remediation where ProjectSend is internet-facing or supports untrusted user accounts.
Technical view
CVE-2018-7202 is an XSS vulnerability affecting ProjectSend before r1053, located in the Name field on the My Account page. The source bundle does not specify whether the XSS is stored or reflected, required privileges, browser interaction, or exact vulnerable versions beyond before r1053.
Likely exposure
Exposure is most likely in ProjectSend deployments running builds earlier than r1053, especially where user account profile fields are accessible to untrusted or lower-trust users.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not claim active exploitation. Public evidence in the bundle is limited to the CVE record and ProjectSend r1053 changelog reference.
Researcher notes
The available record is sparse: no CVSS, CWE, exploit status, or detailed patch note is included in the bundle. Avoid assuming exploitability conditions beyond XSS in the Name field before r1053.
Mitigation direction
- Identify all ProjectSend instances and their build or release level.
- Upgrade deployments earlier than r1053 according to ProjectSend guidance.
- Review the r1053 changelog for the vendor’s stated fix details.
- Restrict account access to trusted users until remediation is complete.
- Monitor ProjectSend guidance for additional affected-version clarification.
Validation and detection
- Confirm production ProjectSend versions are r1053 or later.
- Review whether the My Account Name field sanitizes rendered user input.
- Check web logs for unusual profile-name changes or suspicious account activity.
- Verify no unsupported ProjectSend instances remain externally reachable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2018-7202 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.projectsend.org/change-log-detail/r1053/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.