CVE-2025-11279
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 · uneditedA vulnerability was detected in Axosoft Scrum and Bug Tracking 22.1.1.11545. This issue affects some unknown processing of the component Add Work Item Page. The manipulation of the argument Title results in csv injection. The attack can be launched 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 confidenceCSV injection vulnerability in the Add Work Item Page of Axosoft Scrum and Bug Tracking 22.1.11545 allows remote attackers to inject malicious spreadsheet formulas via the Title field. When exported to CSV, these formulas can execute arbitrary commands when users open the file in spreadsheet applications.
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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Axosoft Scrum and Bug Tracking versionLocate the installed version of Axosoft Scrum and Bug Tracking in the application About or System Information page, or check the software release notes or installation metadataAffected if The installed version is 22.1.11545 exactly, or falls within the 22.1.x release line prior to any patches for this issue
-
Identify CSV export functionalityCheck if the Work Item export feature exists and is accessible via the Add Work Item Page or related work item list views, typically through an Export or Download as CSV optionAffected if CSV export capability is present and exposed to users in the affected version
-
Verify Title field accepts user inputAccess the Add Work Item Page and confirm the Title field accepts text input without server-side sanitization of formula charactersAffected if The Title field accepts arbitrary input including formula characters (=, +, -, @, tab, CR) without validation or escaping
-
Inspect CSV export output for unsanitized dataCreate a test work item with a Title starting with = (for example: =1+2), then export work items to CSV and open the resulting file in a spreadsheet applicationAffected if The CSV export contains raw formula characters in the Title field without escaping (such as prefixing with single quote) and the spreadsheet interprets the content as a formula
You are affected if you are running Axosoft Scrum and Bug Tracking version 22.1.11545 and users can export work items to CSV with unsanitized Title field content that could contain spreadsheet formulas.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation on the Title field to sanitize or reject formula characters (=, +, -, @, tab, CR) before CSV export, and prefix potentially dangerous values with a single quote or apply proper escaping.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11279 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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