dbcve.org
ConfluenceApplication · Mattermost

CVE-2025-54458

MEDIUM · 5.0 CVSS v3.1 Published 2025-08-11
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
56/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
Mattermost Confluence Plugin version <1.5.0 fails to check the access of the user to the Confluence space which allows attackers to create a subscription for a Confluence space the user does not have access to via the create subscription endpoint.

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 · high confidence

The Mattermost Confluence Plugin versions before 1.5.0 lack proper authorization checks on the subscription creation endpoint, allowing authenticated users to subscribe to Confluence spaces they do not have access to. This is an insecure direct object reference (IDOR) vulnerability where the plugin trusts user-supplied space identifiers without verifying the user's permissions against Confluence.

MitigationUpgrade the Mattermost Confluence Plugin to version 1.5.0 or later, which implements proper Confluence space access validation before allowing subscription creation.

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
ConfluenceApplication
Affected:< 1.5.0

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
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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. Identify installed Mattermost Confluence Plugin version
    In Mattermost, go to System Console > Plugins > Plugin Management, locate the Confluence plugin, and note the installed version number. Alternatively, use the CLI: `mattermost plugin list`
    Affected if The plugin version is less than 1.5.0
  2. Confirm the Confluence plugin is enabled and connected
    Verify the Confluence plugin shows as 'Enabled' in the plugin management UI, and check that a Confluence instance URL is configured in the plugin settings
    Affected if The plugin is enabled and has a Confluence instance configured
  3. Review existing space subscriptions for unauthorized access
    Use the Mattermost Confluence plugin commands (such as `/confluence subscriptions list`) or query the plugin API to list all configured space subscriptions. For each subscription, verify whether the subscribing Mattermost user has actual access to that Confluence space in Confluence
    Affected if Any subscription exists for a Confluence space that the subscribing user does not have permission to access in Confluence

You are affected if the Mattermost Confluence Plugin version is below 1.5.0 and the plugin is enabled with Confluence connectivity, regardless of whether unauthorized subscriptions have already been created.

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 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Upgrade the Mattermost Confluence Plugin to version 1.5.0 or later, which implements proper Confluence space access validation before allowing subscription creation.

Recommended fix Moderate confidence

1.5.0 or later

  1. Access the Mattermost instance as an administrator
  2. Navigate to the Mattermost marketplace or plugin management section
  3. Locate the Confluence plugin in the installed plugins list
  4. Update the Confluence plugin to version 1.5.0 or later
  5. Verify the plugin update was successful and the version is now 1.5.0 or higher

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

Fix this in Confluence 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 the upgrade done

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-54458 — 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-54458 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