CVE-2025-1987: Psono-client · XSS or 'Cross-site Scripting'
Affects Psono-clientSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmpsono-clientpkg:npm/psono-clientOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate mitigation should focus on user awareness and operational controls: educate users to avoid importing or interacting with untrusted vault entries, especially those containing suspicious URLs. 2. Implement strict input validation and sanitization on the URL fields within the Psono-client to neutralize javascript: schemes and other potentially malicious payloads. This includes enforcing a whitelist of allowed URL schemes (e.g., https, http) and rejecting or escaping any input that does not conform. 3. Employ Content Security Policy (CSP) headers or equivalent browser security features within the Psono-client to restrict execution of inline scripts and reduce the impact of XSS. 4. Monitor and audit vault entries for anomalous or suspicious URLs, possibly integrating automated scanning tools that flag entries with javascript: or other dangerous schemes. 5. Segregate password vault access environments to limit exposure; for example, restrict Psono-client usage to secure, managed endpoints with endpoint detection and response (EDR) capabilities. 6. Coordinate with Psono and Bitdefender for timely patch deployment once available, and prioritize patching in environments where Psono-client is deployed. 7. Consider multi-factor authentication and additional layers of security around password vault access to mitigate the impact of credential theft. 8. For organizations with custom integrations or automated vault entry imports, implement validation checks to prevent injection of malicious entries.
Description
A Cross-Site Scripting (XSS) vulnerability has been identified in Psono-Client’s handling of vault entries of type website_password and bookmark, as used in Bitdefender SecurePass. The client does not properly sanitize the URL field in these entries. As a result, an attacker can craft a malicious vault entry (or trick a user into creating or importing one) with a javascript:URL. When the user interacts with this entry (for example, by clicking or opening it), the application will execute the malicious JavaScript in the context of the Psono vault. This allows an attacker to run arbitrary code in the victim’s browser, potentially giving them access to the user’s password vault and sensitive data.