CVE-2024-51094
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 · uneditedAn issue in Snipe-IT v.7.0.13 build 15514 allows a low-privileged attacker to modify their profile name and inject a malicious payload into the "Name" field. When an administrator later accesses the People Management page, exports the data as a CSV file, and opens it, the injected payload will be executed, allowing the attacker to exfiltrate internal system data from the CSV file to a remote server.
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 confidenceA CSV injection vulnerability in Snipe-IT v7.0.13 allows low-privileged users to inject malicious formulas (e.g., =HYPERLINK()) into the profile Name field. When an administrator exports user data to CSV and opens it, the injected formulas execute, enabling data exfiltration to remote servers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.0.13CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify Snipe-IT versionAccess the admin dashboard and navigate to Settings > About, or check the installed version via the application footer. Alternatively, check the composer.json or application version file in the installation directory.Affected if The installed version is exactly 7.0.13 (or any version that falls within or below the affected range).
-
Confirm user profile Name field is editableLog in as a low-privileged user (non-admin) and navigate to the profile settings. Attempt to modify the Display Name or Name field.Affected if Low-privilege users can edit their own Name field without restrictions.
-
Check for CSV export functionalityAs an administrator, navigate to the Users section and locate the Export button or option, typically found in the user list view.Affected if CSV export functionality is available and accessible to administrators.
-
Inspect user name fields for formula charactersQuery the users table in the database, or export user data via the admin panel and inspect the Name field values. Look for entries starting with =, +, -, @, or containing characters like =HYPERLINK().Affected if Any user records contain Name field values starting with formula characters (=, +, -, @) or containing suspicious formula-like strings.
The environment is affected if Snipe-IT version is 7.0.13 or within the affected range, low-privilege users can edit their Name field, and the CSV export feature exists and is accessible to administrators.
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 input validation to sanitize or block formula characters (=, +, -, @, tab, carriage return) in user-editable fields, and ensure CSV export properly escapes/formulates data or displays warnings to users before opening.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51094 — 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-2024-51094 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