# CVE-2025-53508: Command injection in F2L Assist-SS-A

> Attackers can execute arbitrary OS commands on iND industrial devices to obtain sensitive information.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-gf66-qjh7-prj2

## What is CVE-2025-53508?

CVE-2025-53508 is a high-severity command injection vulnerability in iND Co.,Ltd F2L Assist-SS-A, published on 29 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple products provided by iND Co.,Ltd contain an OS command injection vulnerability. If exploited, an arbitrary OS command may be executed and sensitive information may be obtained. As for the details of affected product names and versions, refer to the information under [Product Status].

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-53508 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53508 is a high-severity command injection vulnerability in iND Co.,Ltd F2L Assist-SS-A, published on 29 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53508 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-53508/ (Markdown: https://insights.sbomify.com/CVE-2025-53508/index.md)
```

## Sources

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

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