# CVE-2026-112333: GFI Archiver < 15.14 Stored XSS via MailInsights.aspx


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-4cw6-7r4w-2x8v

## What is CVE-2026-112333?

CVE-2026-112333 is a medium-severity vulnerability in GFI Archiver, published on 23 Oct 2026. 

### Official description

GFI Archiver before 15.14 contains a stored cross-site scripting vulnerability in the MailInsights scheduled report configuration that allows authenticated attackers to inject arbitrary web script or HTML via the report name parameter to /Archiver/MailInsights.aspx. The injected payload is stored by ReportScheduling.btnSaveReport_Click() without output encoding and is executed in the browser of the user who created the scheduled report when they subsequently view the MailInsights page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-112333 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112333 is a medium-severity vulnerability in GFI Archiver, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112333 in the wild and no public exploit code.

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

## Sources

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

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