CVE-2023-52257 LogoBee 0.2 allows updates.php?id= XSS.
Medium 6.1
Published
Updated
Check this codebase for CVE-2023-52257 and fix it if it is affected.
What it is: CVE-2023-52257 is a medium-severity vulnerability in n/a, published on 30 Dec 2023.
Exploitation: There is no known exploitation of CVE-2023-52257 in the wild and no public exploit code.
Affected product: n/a. 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-2023-52257/ (Markdown: https://insights.sbomify.com/CVE-2023-52257/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2023-52257?
CVE-2023-52257 is a medium-severity vulnerability in n/a, published on 30 Dec 2023.
Official description
LogoBee 0.2 allows updates.php?id= XSS.
Weakness: CWE-79
Which versions are affected by CVE-2023-52257?
It affects 1 product.
Products include Logobee Logobee.
How do I fix CVE-2023-52257?
No fix has been published for CVE-2023-52257 yet. Limit exposure of the affected software until one is available.
Is CVE-2023-52257 being exploited?
There is no known exploitation of CVE-2023-52257 in the wild and no public exploit code.
Sources
Also known as GHSA-fgwv-c9xg-jwvc.