dbcve.org
ConfluenceApplication · Mattermost

CVE-2025-54478

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-11
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 enforce authentication of the user to the Mattermost instance which allows unauthenticated attackers to edit channel subscriptions via API call to the edit channel 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 prior to 1.5.0 lacks proper authentication enforcement on the edit channel subscription API endpoint, allowing any unauthenticated attacker to modify channel subscriptions by making direct API calls.

MitigationUpgrade the Mattermost Confluence Plugin to version 1.5.0 or later which includes proper authentication validation on the channel subscription endpoints.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm Mattermost Confluence Plugin installation
    In Mattermost, go to Product Menu > Marketplace and search for 'Confluence' or check System Console > Plugins > Plugin Management for an entry named 'Confluence' or 'mattermost-confluence-plugin'.
    Affected if The plugin appears in the installed plugins list.
  2. Identify installed plugin version
    In System Console > Plugins > Plugin Management, locate the Confluence plugin and note the version number displayed next to it.
    Affected if The version number is lower than 1.5.0 (e.g., 1.4.0, 1.3.0, etc.).
  3. Verify channel subscription feature is configured
    Check if the Confluence plugin has been configured with channel subscriptions. Look in System Console > Plugins > Confluence Plugin or check the plugin's settings in a team channel using the /confluence command. Look for subscription-related configuration.
    Affected if Channel subscriptions are configured and the plugin is enabled.
  4. Check API endpoint exposure
    The vulnerable endpoint is the edit channel subscription API (typically at /plugins/confluence/v1/channels/{channel_id}/subscriptions). This can be tested by making an unauthenticated HTTP request to this path on the Mattermost server.
    Affected if The server responds to unauthenticated requests on the Confluence plugin API endpoints (returns 200 or other non-401 status).

If the Confluence plugin is installed with version below 1.5.0 and channel subscriptions are configured, the environment is vulnerable to unauthenticated subscription modification.

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 includes proper authentication validation on the channel subscription endpoints.

Recommended fix High confidence

1.5.0

  1. 1. Log in to the Mattermost System Console as an administrator
  2. 2. Navigate to the Plugin Management or Marketplace section
  3. 3. Locate the 'Confluence' plugin in the list of installed plugins
  4. 4. Update the Confluence plugin to version 1.5.0 or later
  5. 5. Verify the plugin shows version 1.5.0 or higher as installed
  6. 6. Test that channel subscription editing now requires authentication

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
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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