CVE-2026-79627 Advanced File Manager 5.4.13 - 5.4.14 - Authenticated Stored XSS via SVG Sanitiser Content-Sniff Bypass
High 7.1
Published
Updated
Check this codebase for CVE-2026-79627 and fix it if it is affected.
What it is: CVE-2026-79627 is a high-severity vulnerability in Unknown Advanced File Manager, published on 21 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-79627 in the wild and no public exploit code.
Affected product: Unknown Advanced File Manager. 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-79627/ (Markdown: https://insights.sbomify.com/CVE-2026-79627/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-79627?
CVE-2026-79627 is a high-severity vulnerability in Unknown Advanced File Manager, published on 21 Oct 2026.
Official description
The Advanced File Manager WordPress plugin before 6.0.0 does not correctly determine whether a stored file is an SVG before sanitising it, allowing users granted file-manager access by an administrator to store a file containing script that is not stripped and that runs in the browser of anyone who opens it, including an administrator.
Weakness: CWE-79
Which versions are affected by CVE-2026-79627?
How do I fix CVE-2026-79627?
No fix has been published for CVE-2026-79627 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-79627 being exploited?
There is no known exploitation of CVE-2026-79627 in the wild and no public exploit code.
Sources
Also known as GHSA-3846-mpmc-4v59.