# CVE-2025-50126: Extension - rsjoomla.com - Stored XSS vulnerability RSBlog! component 1.11.6-1.14.5 for Joomla

> Authenticated attackers can inject arbitrary scripts via the tags_text parameter in the RSBlog Joomla component, potentially compromising user sessions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2025
- **Updated:** 23 Jul 2025
- **Also known as:** GHSA-95g3-5j3x-8jq6

## What is CVE-2025-50126?

CVE-2025-50126 is a medium-severity cross-site scripting vulnerability in rsjoomla.com RSBlog! component for Joomla, published on 18 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A stored XSS vulnerability in the RSBlog! component 1.11.6-1.14.5 Joomla was discovered. The issue allows remote authenticated users to inject arbitrary web script or HTML via the jform[tags_text] parameter.

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

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


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

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

## Is CVE-2025-50126 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50126 is a medium-severity cross-site scripting vulnerability in rsjoomla.com RSBlog! component for Joomla, published on 18 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50126 in the wild and no public exploit code.

Affected product: rsjoomla.com RSBlog! 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-50126/ (Markdown: https://insights.sbomify.com/CVE-2025-50126/index.md)
```

## Sources

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

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