CVE-2025-12249VulnerabilityPublished 27 Oct 2025

CVE-2025-12249: Axosoft Scrum and Bug Tracking · CSV Injection

Affects Axosoft Scrum and Bug TrackingSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Axosoft Scrum and Bug Tracking	Affected =22.1.1.11545	Fixed in–

AI-suggested

1. Implement strict input validation and sanitization on all user-supplied data fields, especially the 'Title' field in the Edit Ticket Page, to neutralize any characters that could be interpreted as spreadsheet formulas (e.g., '=', '+', '-', '@'). 2. Apply output encoding or escape potentially dangerous characters before exporting data to CSV files to prevent formula execution. 3. Educate users to open CSV files in text editors or spreadsheet applications with formula execution disabled or in protected view modes. 4. Restrict access to the Axosoft Scrum and Bug Tracking web interface to trusted networks and users to reduce exposure to remote attacks. 5. Monitor logs for unusual input patterns or repeated attempts to inject malicious content. 6. If feasible, disable CSV export functionality temporarily until a vendor patch or official fix is available. 7. Maintain up-to-date backups of project data to enable recovery in case of compromise. 8. Engage with the vendor for updates and consider alternative tools if the vendor remains unresponsive. 9. Employ network-level protections such as Web Application Firewalls (WAF) to detect and block injection attempts targeting the vulnerable parameter.

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.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to the confidentiality and integrity of data managed within Axosoft Scrum and Bug Tracking systems. Attackers could inject malicious formulas into CSV exports, which when opened by users, might execute arbitrary commands or scripts, potentially leading to data leakage or further compromise of user systems. This is particularly concerning for organizations that rely heavily on Axosoft for project management and bug tracking, as sensitive project data or internal communications could be exposed or manipulated. The remote and unauthenticated nature of the exploit increases the attack surface, especially for organizations with externally accessible instances of the affected software. While availability impact is limited, the reputational damage and operational disruption from data integrity breaches could be significant. The absence of vendor patches means prolonged exposure until mitigations are implemented. European entities in sectors such as software development, IT services, and critical infrastructure that use Axosoft products are at heightened risk.

Summary

CVE-2025-12249 identifies a CSV Injection vulnerability in Axosoft Scrum and Bug Tracking version 22.1.1.11545, specifically within the Edit Ticket Page component. The vulnerability arises when an attacker manipulates the 'Title' field input, which is later exported into CSV files without proper sanitization or escaping. CSV Injection, also known as Formula Injection, occurs when malicious spreadsheet formulas are embedded in CSV data fields. When such CSV files are opened in spreadsheet applications like Microsoft Excel or LibreOffice Calc, the formulas can execute arbitrary commands, potentially leading to data exfiltration, system compromise, or further malware deployment. This vulnerability can be triggered remotely without requiring authentication or user interaction, increasing its risk profile. The vendor was notified but has not issued any patches or mitigation guidance. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the attack vector is network-based with low complexity and no privileges or user interaction needed, but with limited impact on confidentiality, integrity, and availability. No known exploits are currently observed in the wild, but public exploit code availability raises the risk of exploitation. The lack of vendor response and patch availability means organizations must rely on internal controls and mitigations to reduce exposure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 08:34 UTC

Technical details

References

Community reviews

Related threats