# CVE-2026-94132: File upload in AcyMailing Enterprise extension for Joomla

> Attackers can upload PHP files via email to the monitored mailbox, leading to remote code execution on the Joomla server.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-x2ch-94w5-cr2g

## What is CVE-2026-94132?

CVE-2026-94132 is a critical vulnerability in acymailing.com AcyMailing Enterprise extension for Joomla, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla Extension - acymailing.com - Remote Code Execution vulnerability in mailbox action feature in AcyMailing Enterprise extension < 11.1.0 - MIME parts of incoming emails were saved to media/com_acym/upload/ with no extension check, so anyone who could email the monitored mailbox could write a PHP file into the web root.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Acymailing Acymailing.

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

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

## Is CVE-2026-94132 being exploited?

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

Public exploit code:

- AcyMailing Enterprise for Joomla < 11.1.0: POP3 mailbox actions save MIME attachments without extension checks to media/com_acym/upload/, enabling RCE when an attacker can email the monitored inbox (CVE-2026-94132, CVSS 9.5). Python check/exploit PoC —  (github_poc): https://github.com/murrez/CVE-2026-94132

## Other vulnerabilities in acymailing.com AcyMailing Enterprise extension for Joomla

- [CVE-2023-28731](https://insights.sbomify.com/CVE-2023-28731/): Unauthenticated RCE affecting the AcyMailing plugin for Joomla (critical 9.8)
- [CVE-2026-56292](https://insights.sbomify.com/CVE-2026-56292/): Joomla Extension - acymailing.com - SQL Injection in AcyMailing extension < 10.11.1 (critical 9.2)
- [CVE-2026-94131](https://insights.sbomify.com/CVE-2026-94131/): Joomla Extension - acymailing.com - Unauthenticated arbitrary file deletion in AcyMailing Enterprise extension < 11.1.0 (high 8.3)
- [CVE-2024-7384](https://insights.sbomify.com/CVE-2024-7384/): AcyMailing <= 9.7.2 - Authenticated (Subscriber+) Arbitrary File Upload via acym_extractArchive Function (high 7.5)
- [CVE-2023-28733](https://insights.sbomify.com/CVE-2023-28733/): Stored XSS affecting the AcyMailing plugin for Joomla (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94132 is a critical vulnerability in acymailing.com AcyMailing Enterprise extension for Joomla, published on 26 Sep 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-94132 in the wild and no public exploit code.

Affected product: acymailing.com AcyMailing Enterprise 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-94132/ (Markdown: https://insights.sbomify.com/CVE-2026-94132/index.md)
```

## Sources

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

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