CVE-2025-51965: OURPHP thru 8.6.1 is vulnerable to Cross-Site Scripting (XSS) via the "Name" field of the "Complete Profile...
OURPHP thru 8.6.1 is vulnerable to Cross-Site Scripting (XSS) via the "Name" field of the "Complete Profile" functionality under the "My User Center" page, which can be accessed after registering through the front-end interface.
Security readout for executives and security teams
Plain-English summary
This is a medium-severity cross-site scripting issue in OURPHP through 8.6.1. A malicious value in the user profile Name field could run script in another user’s browser when viewed. Business impact is mainly account trust, session exposure, and content manipulation, not server takeover.
Executive priority
Treat as a normal-priority remediation for exposed OURPHP sites, higher if registration is public or administrators view user profiles. There is no sourced evidence of active exploitation, but XSS can support credential theft and session abuse.
Technical view
CVE-2025-51965 is CWE-79 XSS in the Complete Profile function under My User Center after front-end registration. CVSS 3.1 is 6.1 with network access, low complexity, no privileges, required user interaction, changed scope, and low confidentiality and integrity impact.
Likely exposure
Exposure is most likely on internet-facing OURPHP deployments through 8.6.1 that allow front-end registration and profile completion. The provided CVE metadata does not name CPEs, package identifiers, hosting patterns, or vulnerable code paths beyond the Name field.
Exploitation context
The source bundle does not cite CISA KEV listing or active exploitation. Exploitation would require a vulnerable OURPHP site and a victim interaction path where the crafted profile Name value is rendered in a browser.
Researcher notes
The record identifies the vulnerable feature and field but leaves affected vendor/product metadata as n/a and does not provide patch details. Analysis should stay tied to OURPHP through 8.6.1, CWE-79, and the referenced Yuque advisory until vendor guidance adds clarity.
Mitigation direction
Check OURPHP guidance and release notes for a fixed version or vendor mitigation.
Upgrade from OURPHP through 8.6.1 if a patched release is available.
Apply output encoding and input validation for profile fields, especially Name.
Restrict or monitor front-end registration if immediate patching is unavailable.
Review WAF or application filtering as a temporary compensating control.
Validation and detection
Inventory public sites running OURPHP and identify versions through 8.6.1.
Confirm whether front-end registration and Complete Profile are enabled.
Review templates rendering profile Name for context-aware output encoding.
Use a safe staging test to confirm profile names cannot execute script.
Check user profile data and logs for suspicious Name field 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.