# CVE-2023-31044: Code injection in n/a

> Authenticated attackers can inject malicious payloads into campaign names, leading to code execution or data exfiltration when exported to CSV.

- **Severity:** Low 2.0 (`CVSS:3.1/AC:H/AV:N/A:N/C:L/I:N/PR:H/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-94m7-9fq3-5jf6

## What is CVE-2023-31044?

CVE-2023-31044 is a low-severity code injection vulnerability in n/a, published on 3 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Nokia Impact before Mobile 23_FP1. In Impact DM 19.11 onwards, a remote authenticated user, using the Add Campaign functionality, can inject a malicious payload within the Campaign Name. This data can be exported to a CSV file. Attackers can populate data fields that may attempt data exfiltration or other malicious activity when automatically executed by the spreadsheet software.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-31044?

It affects 1 product.


Products: Nokia Impact Mobile.

## How do I fix CVE-2023-31044?

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

## Is CVE-2023-31044 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-35486](https://insights.sbomify.com/CVE-2021-35486/): Cross-site request forgery in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31044 and fix it if it is affected.

What it is: CVE-2023-31044 is a low-severity code injection vulnerability in n/a, published on 3 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-31044 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-2023-31044/ (Markdown: https://insights.sbomify.com/CVE-2023-31044/index.md)
```

## Sources

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

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