# CVE-2018-25327: Joomla! Component Js Jobs 1.2.0 Cross-Site Request Forgery

> Attackers can trick administrators into deleting job entries or modifying settings via CSRF in the Joomla JS Jobs plugin.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-mpvw-h4vq-pmfx

## What is CVE-2018-25327?

CVE-2018-25327 is a medium-severity vulnerability in Joomsky JS Jobs, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla! Component Js Jobs 1.2.0 contains a cross-site request forgery vulnerability that allows attackers to perform state-changing actions without token validation. Attackers can craft malicious HTML forms targeting administrative endpoints like job.jobenforcedelete to delete job entries or modify component settings when administrators visit attacker-controlled pages.

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

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


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

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

## Is CVE-2018-25327 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25327 is a medium-severity vulnerability in Joomsky JS Jobs, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25327 exists.

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

## Sources

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

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