Rsmail\!Application · Rsjoomla
CVE-2025-30084
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA stored XSS vulnerability in RSMail! component 1.19.20 - 1.22.26 for Joomla was discovered. The issue occurs within the dashboard component, where user-supplied input is not properly sanitized before being stored and rendered. An attacker can inject malicious JavaScript code into text fields or other input points, which is subsequently executed in the browser of any user who clicks on the crafted text in the dashboard.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStored XSS vulnerability in RSMail! Joomla component (versions 1.19.20-1.22.26) within the dashboard component. User-supplied input is not properly sanitized before storage and is rendered without output encoding, allowing injection of malicious JavaScript that executes in the browsers of users viewing the dashboard.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Rsmail\!Application
>= 1.19.20, <= 1.22.26CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm RSMail! component is installedCheck your Joomla site's extensions database table (typically #__extensions) or inspect the /components/com_rsmail/ directory to verify the RSMail! component is present on the system.Affected if The RSMail! component is found installed on the Joomla site.
-
Identify the installed RSMail! versionQuery the Joomla extensions table for the RSMail! component version, or inspect the component's manifest XML file (typically at /components/com_rsmail/rsmail.xml) to retrieve the exact version number.Affected if The installed version is >= 1.19.20 and <= 1.22.26.
-
Verify dashboard component is enabledCheck the Joomla admin panel or extensions table to confirm the RSMail! dashboard component (com_rsmail) is published and enabled.Affected if The RSMail! dashboard component is enabled and accessible to users.
-
Inspect database for unsanitized user inputExamine database tables related to RSMail! (such as any tables prefixed with #__rsmail_) for stored data that may contain unescaped HTML or JavaScript characters like <script>, javascript:, or event handlers (onclick, onerror, etc.).Affected if Stored data in RSMail! tables contains raw HTML/script tags or event handler attributes without encoding.
-
Review dashboard output for encoding issuesIf you have access, view the RSMail! dashboard page source in a browser and check if user-supplied fields (such as campaign names, sender names, or template content) render raw HTML instead of encoded entities.Affected if User-supplied content in the dashboard renders as raw HTML or executes JavaScript.
A system is affected if RSMail! versions 1.19.20 through 1.22.26 are installed with the dashboard component enabled, and unencoded user input can be stored and rendered in the dashboard interface.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply output encoding/sanitization to all user-supplied input before storage and before rendering in the dashboard. Upgrade to the latest RSMail! version if a patch is available.
Fix this in Rsmail\!
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30084 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30084 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data