dbcve.org
Jira AlignApplication · Atlassian

CVE-2025-22175

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-22
Fix available
A fix is available. Upgrade to 11.16.1 or later.
See remediation →
60/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
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to modify the steps of another user's private checklist.

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

Jira Align contains a broken access control vulnerability (likely Insecure Direct Object Reference) where low-privilege users can access or modify resources belonging to other users. Specifically, the vulnerability allows unauthorized modification of private checklist steps belonging to other users, indicating missing or insufficient authorization checks on certain API endpoints.

MitigationImplement proper authorization validation on all API endpoints to ensure users can only access and modify resources they own or have permission to access. Conduct comprehensive access control testing across all user roles.

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
Jira AlignApplication
Affected:>= 11.14.0, < 11.16.1

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

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

  1. Determine installed Jira Align version
    Navigate to Jira Align settings or administration area, typically found under the gear icon or admin console. Look for 'About', 'Version Info', or similar section that displays the current product version number.
    Affected if The displayed version is >= 11.14.0 and < 11.16.1
  2. Identify if Checklist feature is enabled
    In Jira Align, go to the project or portfolio settings. Look for 'Checklists', 'Items', or 'Tasks' feature modules. Check if any checklist-related functionality is active for users.
    Affected if Checklist functionality is available and users have access to create or manage checklist items within projects or portfolios.
  3. Verify API endpoint for checklist operations exists
    Review API documentation or intercept network traffic when using the checklist feature. Identify API endpoints that handle checklist step creation, modification, or deletion. Common patterns include endpoints with '/checklist/', '/items/', or '/steps/' in the path.
    Affected if API endpoints exist that accept POST, PUT, or PATCH requests to modify checklist steps without additional authorization parameters.
  4. Test cross-user access to checklist resources
    As a low-privilege user, create a private checklist with steps in your own workspace. Then attempt to access or modify those same checklist steps using the API while authenticated as a different low-privilege user, by manipulating resource identifiers (such as step IDs, item IDs, or user IDs) in the request.
    Affected if Requests with modified identifiers (pointing to another user's checklist steps) are successfully processed and return 200 OK instead of 403 Forbidden or 404 Not Found.

You are affected if your Jira Align version is between 11.14.0 and 11.15.x inclusive AND the checklist feature is enabled, allowing unauthorized modification of other users' private checklist steps via API.

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.

dbcve · scoped
Upgrade available Upgrade to 11.16.1 or later
Fixed in 11.16.1
Interim mitigation

Implement proper authorization validation on all API endpoints to ensure users can only access and modify resources they own or have permission to access. Conduct comprehensive access control testing across all user roles.

Recommended fix High confidence

11.16.1

  1. Upgrade Jira Align to version 11.16.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jira Align Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22175 — 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-22175 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