# CVE-2025-49486: Extension - balbooa.com - Stored XSS in Balbooa Gallery component version 1.0.0 - 2.4.0 for Joomla

> Privileged users can inject malicious scripts into gallery items, leading to stored XSS attacks against other users.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2025
- **Updated:** 20 Jul 2025
- **Also known as:** GHSA-6wqg-9vx3-jvvm

## What is CVE-2025-49486?

CVE-2025-49486 is a high-severity cross-site scripting vulnerability in balbooa.com Balbooa Gallery component for Joomla, published on 18 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A stored XSS vulnerability in the Balbooa Gallery plugin 1.0.0-2.4.0 for Joomla allows privileged users to store malicious scripts in gallery items.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-49486?


## How do I fix CVE-2025-49486?

No fix has been published for CVE-2025-49486 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-49486 being exploited?

There is no known exploitation of CVE-2025-49486 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49486 and fix it if it is affected.

What it is: CVE-2025-49486 is a high-severity cross-site scripting vulnerability in balbooa.com Balbooa Gallery component for Joomla, published on 18 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-49486 in the wild and no public exploit code.

Affected product: balbooa.com Balbooa Gallery component for Joomla. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-49486/ (Markdown: https://insights.sbomify.com/CVE-2025-49486/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-49486
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-49486
- OSV: https://osv.dev/vulnerability/CVE-2025-49486

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-49486/
Summaries are generated and may contain mistakes; the official description above is the record.