Skip to main content
VulnerabilityPublished Updated

CVE-2024-24061: springboot-manager · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Feb 2024

  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
Mavenspringboot-managerpkg:maven/springboot-managerOther threatsAffected
  • =1.6
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 include restricting access to the /sysContent/add endpoint to trusted users only, ideally via network segmentation or VPNs.
  2. Implement strict input validation and output encoding on all user-supplied data, especially on the vulnerable endpoint, to prevent script injection.
  3. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers.
  4. Monitor logs for unusual activity related to the management interface to detect potential exploitation attempts.
  5. Educate users with access about the risks of interacting with suspicious links or content that could trigger the XSS payload.
  6. If possible, disable or limit the use of the vulnerable feature until a patch is released.
  7. Stay updated with vendor advisories for patches or official fixes and apply them promptly once available.
  8. Conduct regular security assessments and penetration tests focusing on management interfaces to identify similar vulnerabilities.

Description

springboot-manager v1.6 is vulnerable to Cross Site Scripting (XSS) via /sysContent/add.

References

Community reviews

Loading reviews…