# CVE-2018-25354: Joomla Component jomres 9.11.2 Cross-Site Request Forgery

> Attackers can trick authenticated users into modifying account details like passwords and emails via CSRF in the Jomres Joomla component.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **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:** 23 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-w384-fv8f-hx76

## What is CVE-2018-25354?

CVE-2018-25354 is a medium-severity vulnerability in Jomres, published on 23 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Joomla Component jomres 9.11.2 contains a cross-site request forgery vulnerability that allows attackers to modify user account information by tricking authenticated users into visiting malicious pages. Attackers can craft HTML forms targeting the account/index endpoint with hidden fields to change passwords, email addresses, and profile details without user consent.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-25354?


## How do I fix CVE-2018-25354?

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

## Is CVE-2018-25354 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25354 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25354 and fix it if it is affected.

What it is: CVE-2018-25354 is a medium-severity vulnerability in Jomres, published on 23 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25354 exists.

Affected product: Jomres. 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-2018-25354/ (Markdown: https://insights.sbomify.com/CVE-2018-25354/index.md)
```

## Sources

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

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