dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-54990

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
XWiki AdminTools integrates administrative tools for managing a running XWiki instance. Prior to version 1.1, users without admin rights have access to AdminTools.SpammedPages. View rights are not restricted only to admin users for AdminTools.SpammedPages. While no data is visible to non admin users, the page is still accessible. This issue has been patched in version 1.1. A workaround involves setting the view rights for the AdminTools space to be only available for the XWikiAdminGroup.

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

XWiki AdminTools plugin before version 1.1 allows non-admin users to access the AdminTools.SpammedPages page due to improperly configured view rights. Although no sensitive data is displayed to these users, the unauthorized page accessibility itself constitutes an improper access control vulnerability.

MitigationUpgrade AdminTools to version 1.1 or manually restrict view rights on the AdminTools space to the XWikiAdminGroup only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Verify AdminTools plugin is installed
    In XWiki, go to Administration > Extensions and look for the AdminTools extension in the installed list, or query the extension manager via API for 'AdminTools'
    Affected if AdminTools extension appears in the installed extensions list
  2. Determine installed AdminTools version
    In the extensions list, note the version number of the AdminTools plugin. Compare this version to 1.1 using semantic version comparison
    Affected if The installed version is lower than 1.1 (e.g., 1.0.x, 0.x.x)
  3. Check view rights on AdminTools space
    Go to Administration > Rights. Look for rights entries on the 'AdminTools' space or page 'AdminTools.SpammedPages'. Examine which users/groups have View permission
    Affected if Non-admin users (users not in XWikiAdminGroup) or unauthenticated users have View rights on AdminTools.SpammedPages or the AdminTools space
  4. Verify unauthorized access to the vulnerable page
    Log in as a non-admin user (a user NOT in XWikiAdminGroup). Navigate directly to the URL /xwiki/bin/view/AdminTools/SpammedPages or attempt to access this page through the UI
    Affected if The page loads without permission denied error for a non-admin user

A user is affected if AdminTools plugin version is below 1.1 AND non-admin users can view the AdminTools.SpammedPages page due to overly permissive view rights.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade AdminTools to version 1.1 or manually restrict view rights on the AdminTools space to the XWikiAdminGroup only.

Recommended fix Moderate confidence

AdminTools version 1.1

  1. 1. Back up your XWiki instance before performing any upgrade
  2. 2. Navigate to XWiki Administration > Extensions > Extensions Manager
  3. 3. Search for the AdminTools extension
  4. 4. Upgrade the AdminTools extension to version 1.1 or later
  5. 5. Alternatively, install the AdminTools version 1.1 from the XWiki Marketplace
  6. 6. After upgrade, verify that non-admin users can no longer access the AdminTools.SpammedPages page
  7. 7. If upgrade is not immediately possible, apply the workaround: Navigate to XWiki Administration > Rights > AdminTools space and restrict view rights to only XWikiAdminGroup

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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