CVE-2026-120075 WP Activity Log <= 5.6.1 - Unauthenticated Stored Cross-Site Scripting
High 7.2
Published
Updated
Check this codebase for CVE-2026-120075 and fix it if it is affected.
What it is: CVE-2026-120075 is a high-severity vulnerability in melapress WP Activity Log, published on 31 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-120075 in the wild and no public exploit code.
Affected product: melapress WP Activity Log. 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-120075/ (Markdown: https://insights.sbomify.com/CVE-2026-120075/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-120075?
CVE-2026-120075 is a high-severity vulnerability in melapress WP Activity Log, published on 31 Oct 2026.
Official description
The WP Activity Log plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 5.6.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Weakness: CWE-79
Which versions are affected by CVE-2026-120075?
How do I fix CVE-2026-120075?
No fix has been published for CVE-2026-120075 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-120075 being exploited?
There is no known exploitation of CVE-2026-120075 in the wild and no public exploit code.
Sources
Also known as GHSA-2c56-765v-m493.