Quick answers
- Is CVE-2025-60378 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-60378 being exploited in the wild.
- How severe is CVE-2025-60378?
- High severity, with a CVSS score of 8.1, published 10 October 2025.
- Which products and versions are affected?
- Fairsketch RISE Ultimate Project Manager & CRM < 3.9.4.
- Is there a fix for CVE-2025-60378?
- A patch was published on 2025-11-17: NVD record indicates versions up to 3.9.4 are affected; fix available in 3.9.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-60378 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-60378?
- Check whether you run Fairsketch RISE Ultimate Project Manager & CRM or Fairsketch Rise Ultimate Project Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stored HTML injection vulnerability (classified under CWE-79) exists in RISE Ultimate Project Manager & CRM versions prior to 3.9.4. The flaw resides in the invoice and messaging modules, where the application fails to properly neutralize user-supplied input before storing it. An authenticated attacker can inject arbitrary HTML tags that are subsequently rendered in various contexts, including the web-based chat module, generated PDF invoices, and outgoing notification emails. This can be leveraged for credential theft, phishing, or business email compromise. The risk is further amplified by the platform's automated recurring invoice feature, which can distribute the malicious payload to multiple recipients without further attacker interaction. The issue is addressed in version 3.9.4.
Affected products
- Fairsketch RISE Ultimate Project Manager & CRM < 3.9.4
Timeline
- 2025-10-10: advisory
- 2025-11-17: patched: NVD record indicates versions up to 3.9.4 are affected; fix available in 3.9.4.