Skip to main content
CVE-2024-30879VulnerabilityPublished Updated

CVE-2024-30879: rageframe2 · n/a

Affects rageframe2Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Apr 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubjianyan74/rageframe2pkg:github/jianyan74/rageframe2Other threatsAffected
  • =2.6.43
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. Implement strict input validation and sanitization on the boxId parameter to ensure only expected values are accepted, rejecting or encoding any special characters that could be used for script injection. 2. Apply proper output encoding (e.g., HTML entity encoding) on all user-supplied data reflected in the web page to prevent execution of injected scripts. 3. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and mitigate the impact of XSS attacks. 4. Educate users and administrators about the risks of clicking untrusted links and encourage cautious behavior. 5. Monitor web application logs for suspicious requests containing unusual or encoded payloads targeting the image cropping function. 6. If possible, isolate or disable the vulnerable image cropping feature until a vendor patch is available. 7. Stay updated with RageFrame2 vendor announcements for official patches or security advisories and apply them promptly once released. 8. Conduct regular security testing, including automated and manual XSS detection, to identify and remediate similar vulnerabilities proactively.

Description

Reflected Cross Site Scripting (XSS) vulnerability in RageFrame2 v2.6.43, allows remote attackers to execute arbitrary web scripts or HTML and obtain sensitive information via a crafted payload injected into the boxId parameter in the image cropping function.

References

Community reviews

Loading reviews…