# CVE-2025-53507: Information disclosure in F2L Assist-SS-A

> Attackers can access sensitive configuration data, including admin passwords, from iND Co.,Ltd industrial IoT devices due to insecure storage.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-5r7x-gv34-x2cp

## What is CVE-2025-53507?

CVE-2025-53507 is a high-severity vulnerability in iND Co.,Ltd F2L Assist-SS-A, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple products provided by iND Co.,Ltd contain an insecure storage of sensitive information vulnerability. If exploited, configuration information, such as admin password, may be disclosed. As for the details of affected product names and versions, refer to the information under [Product Status].

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2025-53507?


## How do I fix CVE-2025-53507?

No fix has been published for CVE-2025-53507 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53507 being exploited?

There is no known exploitation of CVE-2025-53507 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53507 and fix it if it is affected.

What it is: CVE-2025-53507 is a high-severity vulnerability in iND Co.,Ltd F2L Assist-SS-A, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-53507 in the wild and no public exploit code.

Affected product: iND Co.,Ltd F2L Assist-SS-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-53507/ (Markdown: https://insights.sbomify.com/CVE-2025-53507/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53507
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53507
- OSV: https://osv.dev/vulnerability/CVE-2025-53507

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53507/
Summaries are generated and may contain mistakes; the official description above is the record.