# CVE-2026-64871: Joomla Extension - regularlabs.com - Inconsistent CSRF token checks / privilege checks in Cache Cleaner extension

> Attackers can bypass CSRF and privilege checks to purge administrator caches without proper authorization in the Joomla Cache Cleaner extension.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A: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:** 23 Jul 2026
- **Updated:** 25 Jul 2026
- **Also known as:** GHSA-49jw-c4hx-66m6

## What is CVE-2026-64871?

CVE-2026-64871 is a medium-severity vulnerability in regularlabs.com Cache Cleaner extension for Joomla, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Joomla Extension - regularlabs.com - Inconsistent CSRF token checks / privilege checks in Cache Cleaner extension - Administrator URL purges did not consistently require a valid token and cache-management permission.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-64871?


## How do I fix CVE-2026-64871?

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

## Is CVE-2026-64871 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64871 and fix it if it is affected.

What it is: CVE-2026-64871 is a medium-severity vulnerability in regularlabs.com Cache Cleaner extension for Joomla, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64871 in the wild and no public exploit code.

Affected product: regularlabs.com Cache Cleaner extension 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-2026-64871/ (Markdown: https://insights.sbomify.com/CVE-2026-64871/index.md)
```

## Sources

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

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