# CVE-2025-12249: Axosoft Scrum and Bug Tracking Edit Ticket csv injection

> Remote attackers can inject malicious CSV data via the ticket title field in Axosoft Scrum and Bug Tracking, potentially affecting data integrity.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 27 Oct 2025
- **Also known as:** GHSA-gjvx-9qg7-hc38

## What is CVE-2025-12249?

CVE-2025-12249 is a medium-severity vulnerability in Axosoft Scrum and Bug Tracking, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in Axosoft Scrum and Bug Tracking 22.1.1.11545. The impacted element is an unknown function of the component Edit Ticket Page. Performing manipulation of the argument Title results in csv injection. It is possible to initiate the attack remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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


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

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

## Is CVE-2025-12249 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12249 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12249 is a medium-severity vulnerability in Axosoft Scrum and Bug Tracking, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12249 exists.

Affected product: Axosoft Scrum and Bug Tracking. 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-12249/ (Markdown: https://insights.sbomify.com/CVE-2025-12249/index.md)
```

## Sources

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

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