CVE-2021-30125
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 · uneditedJamf Pro before 10.28.0 allows XSS related to inventory history, aka PI-009376.
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 stored Cross-Site Scripting (XSS) vulnerability exists in Jamf Pro versions prior to 10.28.0. The vulnerability is specifically related to the inventory history feature, where malicious JavaScript code can be injected into inventory data and executed when viewed by other users, likely Jamf administrators.
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< 10.28.0CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify Jamf Pro versionLog into the Jamf Pro admin console and navigate to Settings > System Settings > About, or check the version displayed on the login page. Alternatively, check the build info via the API endpoint /health or the jamf-pro server logs.Affected if The installed version is anything less than 10.28.0 (e.g., 10.27.x, 10.26.x, earlier versions).
-
Confirm inventory history feature accessVerify that user accounts with access to Jamf Pro have permission to view computer or mobile device inventory history. Check Jamf Pro user accounts and group privileges under Users & Groups > Accounts > Privileges.Affected if Any administrative or privileged user account has access to view inventory history records, which is the default configuration for most admin-level accounts.
-
Identify inventory record injection pointsReview the inventory information stored for computers or mobile devices. Examine custom attributes, extension attributes, or user-editable fields that accept input and are displayed in the inventory history view.Affected if The Jamf Pro database contains inventory records with custom data that could have been populated through the self-service portal, MDM enrollment, or administrative imports.
You are affected if your Jamf Pro version is below 10.28.0 and users with inventory history view privileges exist in the system.
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 data10.28.0
Upgrade Jamf Pro to version 10.28.0 or later to resolve this vulnerability. Additionally, implement Content Security Policy headers and validate input sanitization as defense-in-depth measures.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30125 — 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-2021-30125 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