CVE-2025-52182 Information disclosure in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2025-52182 and fix it if it is affected.
What it is: CVE-2025-52182 is a high-severity vulnerability in n/a, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52182 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-2025-52182/ (Markdown: https://insights.sbomify.com/CVE-2025-52182/index.md)
An information disclosure vulnerability in LS2 Admin allows attackers to access sensitive data without proper authentication.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-52182?
CVE-2025-52182 is a high-severity vulnerability in n/a, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Library Corporation LS2 Admin v5.7 to v5.8.0 was discovered to contain an information disclosure vulnerability.
Weakness: CWE-306
Which versions are affected by CVE-2025-52182?
How do I fix CVE-2025-52182?
No fix has been published for CVE-2025-52182 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-52182 being exploited?
There is no known exploitation of CVE-2025-52182 in the wild and no public exploit code.
Sources
Also known as GHSA-8h4w-q22c-8wqm.