CVE-2025-27754: rsjoomla.com RSBlog component for Joomla · Cross-site Scripting
Affects rsjoomla.com RSBlog component for JoomlaSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 5 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
Packagistrsjoomla/rsblogpkg:composer/rsjoomla/rsblogOther threats | Affected
| 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 involves restricting access to the RSBlog! component to trusted users only and monitoring for suspicious activity from authenticated users. 2. Implement strict input validation and output encoding on all user-supplied data within the RSBlog! component, especially for fields that accept HTML or script content. 3. Apply Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on the website. 4. Regularly update Joomla and all installed extensions, including RSBlog!, as soon as official patches or updates addressing this vulnerability are released by the vendor. 5. Conduct thorough security audits and penetration testing focusing on web application vulnerabilities, including stored XSS. 6. Educate administrators and users about the risks of XSS and the importance of secure authentication practices to prevent account compromise. 7. Consider deploying Web Application Firewalls (WAFs) with rules designed to detect and block XSS payloads targeting Joomla components. 8. Monitor logs for unusual script injections or anomalous user behavior that could indicate exploitation attempts.
Description
A stored XSS vulnerability in RSBlog! component 1.11.6 - 1.14.4 for Joomla was discovered. The vulnerability allows authenticated users to inject malicious JavaScript into the plugin's resource. The injected payload is stored by the application and later executed when other users view the affected content.