CVE-2025-45236: A stored cross-site scripting (XSS) vulnerability in the Edit Profile feature of DBSyncer v2.0.6 allows att...
A stored cross-site scripting (XSS) vulnerability in the Edit Profile feature of DBSyncer v2.0.6 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the Nickname parameter.
Security readout for executives and security teams
Plain-English summary
CVE-2025-45236 is a stored XSS issue in DBSyncer v2.0.6. A logged-in attacker can save malicious content in the Edit Profile Nickname field. When another user views the stored content, browser-side script may run, potentially exposing user data or altering page behavior.
Executive priority
Treat as a moderate-priority application security issue. It is unlikely to cause system compromise alone, but it can affect user sessions and trust in an internal administration tool if unremediated.
Technical view
The CVE describes CWE-79 stored cross-site scripting in the Edit Profile feature of DBSyncer v2.0.6, specifically the Nickname parameter. CVSS 3.1 is 5.4: network reachable, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.
Likely exposure
Organizations running DBSyncer v2.0.6 with user accounts that can edit profile nicknames are potentially exposed. The source bundle does not identify CPEs, packaged distributions, or broader affected versions.
Exploitation context
Sources do not indicate active exploitation, and the CVE is not listed as KEV in the provided data. Exploitation requires an authenticated user to store malicious input and a victim user to view the affected profile context.
Researcher notes
The public record is narrow: DBSyncer v2.0.6, Edit Profile, Nickname parameter, stored XSS. No patch version, vendor advisory, or exploit-in-the-wild evidence is provided in the source bundle. Avoid assuming other versions are affected without testing or vendor confirmation.
Mitigation direction
Check the DBSyncer project and CVE references for vendor remediation guidance.
Restrict access to DBSyncer accounts until remediation is confirmed.
Review profile fields for unsafe stored HTML or script content.
Apply input validation and output encoding if maintaining a local fork.
Validation and detection
Inventory DBSyncer deployments and confirm whether v2.0.6 is in use.
Review application code handling the Edit Profile Nickname parameter.
Check whether profile nickname output is HTML-encoded in rendered pages.
Review logs and stored profile data for suspicious nickname content.
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.