Skip to main content
VulnerabilityPublished

CVE-2025-7672: JiranSoft CrossEditor4 · XSS or 'Cross-site Scripting'

Affects JiranSoft CrossEditor4Source CVE Database V5

0

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
JiranSoft CrossEditor4Affected
  • =4.0.0.01
Fixed in–

AI-suggested

  1. Upgrade CrossEditor4 to version 4.6.0.23 or later, where this vulnerability is addressed.
  2. If immediate upgrade is not possible, implement strict input validation and output encoding on all user inputs processed by CrossEditor4, especially in API modules.
  3. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing CrossEditor4.
  4. Conduct regular security awareness training to help users recognize and avoid phishing attempts that could exploit this vulnerability.
  5. Monitor web application logs for unusual input patterns or script injection attempts.
  6. Limit user privileges within CrossEditor4 to reduce the impact of potential script execution.
  7. Use web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting CrossEditor4 endpoints.
  8. Review and harden default permission settings related to CrossEditor4 API modules to prevent unauthorized access or misuse.

Description

The improper default setting in JiranSoft CrossEditor4 on Windows, Linux, Unix (API modules) potentaily allows Stored XSS. This issue affects CrossEditor4: from 4.0.0.01 before 4.6.0.23.

References

Community reviews

Loading reviews…