# CVE-2026-110505: Enable SVG, WebP, and ICO Upload < 1.1.6 - Author+ Stored XSS via SMIL Animation Bypass


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-cghp-w6p2-hcf7

## What is CVE-2026-110505?

CVE-2026-110505 is a medium-severity vulnerability in Unknown Enable SVG, WebP, and ICO Upload, published on 29 Oct 2026. 

### Official description

The Enable SVG, WebP, and ICO Upload WordPress plugin before 1.1.6 does not prevent animation elements in uploaded SVG files from changing a link's target to a javascript: URI, which could allow users with the author role and above to bypass its SVG sanitization and perform Stored Cross-Site Scripting attacks that execute in WebKit-based browsers such as Safari.

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

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


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

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

## Is CVE-2026-110505 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110505 is a medium-severity vulnerability in Unknown Enable SVG, WebP, and ICO Upload, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110505 in the wild and no public exploit code.

Affected product: Unknown Enable SVG, WebP, and ICO Upload. 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-110505/ (Markdown: https://insights.sbomify.com/CVE-2026-110505/index.md)
```

## Sources

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

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