CVE-2026-123197 WPPConnect Server through 2.10.76 Unauthenticated Sticker Media Disclosure via /files
Medium 6.9
Published
Updated
Check this codebase for CVE-2026-123197 and fix it if it is affected.
What it is: CVE-2026-123197 is a medium-severity vulnerability in wppconnect-server, published on 5 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-123197 in the wild and no public exploit code.
Affected product: wppconnect-server. 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-123197/ (Markdown: https://insights.sbomify.com/CVE-2026-123197/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-123197?
CVE-2026-123197 is a medium-severity vulnerability in wppconnect-server, published on 5 Nov 2026.
Official description
WPPConnect Server through 2.10.76 contains a missing authentication vulnerability that allows unauthenticated attackers to read decrypted sticker media through the /files static mount. Attackers can enumerate Unix timestamps in GET /files/file<timestamp>.webp requests to retrieve stickers from any session, bypassing per-session token checks.
Weakness: CWE-552
Which versions are affected by CVE-2026-123197?
How do I fix CVE-2026-123197?
No fix has been published for CVE-2026-123197 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-123197 being exploited?
There is no known exploitation of CVE-2026-123197 in the wild and no public exploit code.
Sources
Also known as GHSA-r9xw-h7vq-jh5r.