Skip to main content
VulnerabilityPublished

CVE-2025-40975: WorkDo HRMGo · XSS or 'Cross-site Scripting'

Affects WorkDo HRMGoSource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jan 2026

  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
WorkDoHRMGoAffected
  • =All versions
Fixed in–

AI-suggested

Organizations should implement strict input validation and output encoding on the 'description' parameter to neutralize malicious scripts before rendering. Until official patches are released by WorkDo, applying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting '/hrmgo/ticket/changereply' can reduce risk. Restricting user privileges to the minimum necessary and educating users about the risks of interacting with untrusted content can limit exploitation opportunities. Monitoring logs for unusual POST requests or anomalous user behavior related to ticket replies can help detect attempted exploitation. Additionally, organizations should engage with WorkDo for timely patch releases and consider isolating HRMGo instances from broader networks to contain potential breaches. Regular security assessments and penetration testing focusing on XSS vectors in HRMGo are recommended. Finally, enforcing Content Security Policy (CSP) headers can mitigate the impact of successful XSS by restricting script execution contexts.

Description

Stored Cross-Site Scripting (XSS) vulnerability in WorkDo's HRMGo, consisting of a lack of proper validation of user input by sending a POST request to ‘/hrmgo/ticket/changereply’, using the ‘description’ parameter.

References

Community reviews

Loading reviews…