# CVE-2026-67361: File upload in J2Store extension for Joomla

> Unauthenticated attackers can upload malicious files to J2Store due to missing CSRF protection and directory safeguards, potentially leading to remote code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:A/R:A`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-2vmq-jqv2-9gfv

## What is CVE-2026-67361?

CVE-2026-67361 is a medium-severity vulnerability in j2commerce.com J2Store extension for Joomla, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla Extension - j2commerce.com - Unauthenticated file upload with missing directory protection in J2Store 1.0.0-3.3.20, 4.0.0-4.0.20, 4.1.0-4.1.5 - The file upload endpoint accepted POST requests from unauthenticated visitors with no CSRF token. Compounding this, the installer manifest omitted the upload and invoices directories, causing fresh installs to deploy those directories without .htaccess/web.config protection, making uploaded files directly web-accessible.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-67361 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67361 is a medium-severity vulnerability in j2commerce.com J2Store extension for Joomla, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67361 in the wild and no public exploit code.

Affected product: j2commerce.com J2Store 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-67361/ (Markdown: https://insights.sbomify.com/CVE-2026-67361/index.md)
```

## Sources

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

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