Skip to main content
VulnerabilityPublished Updated

CVE-2024-39143: ResidenceCMS · Cross-site Scripting

Affects ResidenceCMSSource CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% 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

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 2 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

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

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by MITRE Corporation

    , 11 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    ResidenceCMS 2.10.1 - Stored Cross-Site Scripting (XSS)

    , 281 days after disclosure

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
GitHubcoderberg/ResidenceCMSpkg:github/coderberg/ResidenceCMSOther threatsAffected
  • =2.10.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-39143, organizations should prioritize upgrading ResidenceCMS to a patched version once available. In the absence of official patches, implement strict input validation to disallow or sanitize HTML tags and scripts in property content fields. Employ robust output encoding (e.g., HTML entity encoding) when rendering user-generated content to prevent script execution. Use Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce XSS impact. Conduct regular security audits and penetration testing focused on input handling. Limit user privileges to the minimum necessary and monitor logs for suspicious content submissions. Educate users about the risks of clicking untrusted links within the CMS. Additionally, consider deploying web application firewalls (WAFs) with XSS detection rules tailored to ResidenceCMS traffic patterns. These combined measures reduce the likelihood and impact of exploitation.

Description

A stored cross-site scripting (XSS) vulnerability exists in ResidenceCMS 2.10.1 that allows a low-privilege user to create malicious property content with HTML inside which acts as a stored XSS payload.

References

Community reviews

Loading reviews…