dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32466

MEDIUM · 6.7 CVSS v4.0 Published 2025-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A SQL injection vulnerability in RSMediaGallery! component 1.7.4 - 2.1.7 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 confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in the RSMediaGallery! Joomla component (versions 1.7.4-2.1.7) within the dashboard. User-supplied input is not sanitized before storage and is rendered without proper output encoding, allowing injection of malicious JavaScript that executes in the browser of any user viewing the affected dashboard elements.

MitigationImplement proper input validation and output encoding/sanitization on all user-supplied fields in the dashboard component before storage and before rendering to prevent JavaScript execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Authentication
None
User interaction
A
Scope
N

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:X/V:X/RE:L/U:Clear

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify RSMediaGallery component is installed
    Access the Joomla administrator panel and navigate to Components > RSMediaGallery. If the component appears in the menu, it is installed.
    Affected if RSMediaGallery component is present in the Joomla installation
  2. Determine the installed RSMediaGallery version
    In the Joomla administrator panel, go to Components > RSMediaGallery and look for the version information typically displayed in the component header or about section. Alternatively, check the manifest file in /administrator/components/com_rsmediagallery/rsmediagallery.xml for the version attribute.
    Affected if The version number falls within the range 1.7.4 through 2.1.7 (inclusive)
  3. Confirm dashboard functionality is accessible
    Navigate to the RSMediaGallery dashboard area in the administrator panel (usually Components > RSMediaGallery > Dashboard). Verify that the dashboard interface loads and accepts user input.
    Affected if The dashboard interface is accessible and functional
  4. Identify affected dashboard input fields
    Review the dashboard form fields where user-supplied data can be entered (such as title fields, description fields, custom text inputs, or media configuration settings). These are the locations where unsanitized input could be stored.
    Affected if User-editable fields exist in the dashboard that accept and store input without visible sanitization

The environment is affected if RSMediaGallery is installed with a version between 1.7.4 and 2.1.7 and the dashboard with user-editable fields is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding/sanitization on all user-supplied fields in the dashboard component before storage and before rendering to prevent JavaScript execution.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32466 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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