CVE-2025-52164 Hardcoded credentials in n/a
High 8.2
Published
Updated
Check this codebase for CVE-2025-52164 and fix it if it is affected.
What it is: CVE-2025-52164 is a high-severity vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52164 exists.
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-52164/ (Markdown: https://insights.sbomify.com/CVE-2025-52164/index.md)
Agorum core stores user credentials in plaintext, allowing attackers with access to the storage to read them and potentially take over accounts.
- 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-52164?
CVE-2025-52164 is a high-severity vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Software GmbH Agorum core open v11.9.2 & v11.10.1 was discovered to store credentials in plaintext.
Weakness: CWE-256
Which versions are affected by CVE-2025-52164?
How do I fix CVE-2025-52164?
No fix has been published for CVE-2025-52164 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-52164 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52164 exists.
Sources
Also known as GHSA-85f8-38hh-c6gj.