dbcve.org
InjectionWeakness · CWE-74

CVE-2025-12249

MEDIUM · 6.3 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CSV injection vulnerability in Axosoft Scrum and Bug Tracking's Edit Ticket Page allows remote attackers to inject malicious formulas via the Title argument. When ticket data is exported to CSV format, the injected formulas (e.g., starting with =, +, -, @) can execute arbitrary commands or perform data exfiltration when opened in spreadsheet applications.

MitigationImplement input validation and output encoding for the Title field to neutralize formula injection characters (=, +, -, @, tab, CR). Alternatively, prepend a single quote (') to any field starting with these characters during CSV export to force spreadsheet applications to treat them as text.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Axosoft Scrum and Bug Tracking is installed
    Check for the application via installed programs list, web server running on common ports (typically 80/443), or look for axosoft-related processes and services on the system
    Affected if Axosoft Scrum and Bug Tracking software is present and running on the system
  2. Determine the installed version
    Check the application's About page, login screen footer, or configuration files for version information. Compare against any known affected version ranges for this product.
    Affected if The installed version falls within any affected version range of Axosoft Scrum and Bug Tracking
  3. Verify ticket creation and Title field access
    Log into the application as a standard user, navigate to the ticket creation or edit page, and confirm the Title field is accessible and accepts user input
    Affected if A user can access the ticket edit/create page and input data into the Title field
  4. Confirm CSV export functionality exists
    Create or open an existing ticket, look for an export option (typically in ticket list view or ticket details), and verify CSV export is available and functional
    Affected if The application has CSV export capability for ticket data
  5. Check if Title field lacks formula injection protection
    Create a test ticket with a Title beginning with =, +, -, or @ characters. Export tickets to CSV and open the resulting file in a spreadsheet application to observe if the formula executes or is treated as text.
    Affected if The exported CSV file interprets values starting with =, +, -, or @ as formulas rather than plain text (no sanitization is present)

The environment is affected if Axosoft Scrum and Bug Tracking is running with a vulnerable version, the Title field is accessible to users, CSV export functionality exists, and the Title field does not sanitize formula injection characters before CSV export.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding for the Title field to neutralize formula injection characters (=, +, -, @, tab, CR). Alternatively, prepend a single quote (') to any field starting with these characters during CSV export to force spreadsheet applications to treat them as text.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12249 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12249 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data