# CVE-2025-55703: SQL injection in n/a

> Attackers can manipulate SQL queries via an outdated API endpoint in Power IQ, potentially reading or modifying data.

- **Severity:** Low 2.5 (`CVSS:3.1/AC:H/AV:L/A:N/C:L/I:N/PR:L/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Dec 2025
- **Updated:** 15 Dec 2025
- **Also known as:** GHSA-rrmq-h575-f8r5

## What is CVE-2025-55703?

CVE-2025-55703 is a low-severity SQL injection vulnerability in n/a, published on 15 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An error-based SQL injection vulnerability exists in the Sunbird Power IQ 9.2.0 API. The vulnerability is due to an outdated API endpoint that applied arrays without proper input validation. This can allow attackers to manipulate SQL queries. This has been addressed in Power IQ version 9.2.1, where the API call code was updated to ensure safe handling of input values.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Sunbirddcim Power Iq.

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

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

## Is CVE-2025-55703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55703 is a low-severity SQL injection vulnerability in n/a, published on 15 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-55703 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-55703/ (Markdown: https://insights.sbomify.com/CVE-2025-55703/index.md)
```

## Sources

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

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