dbcve.org
CWE-552Weakness · CWE-552

CVE-2026-24732

MEDIUM · 6.6 CVSS v4.0 Published 2026-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
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
Files or Directories Accessible to External Parties, Incorrect Permission Assignment for Critical Resource vulnerability in Hallo Welt! GmbH BlueSpice (Extension:NSFileRepo modules) allows Accessing Functionality Not Properly Constrained by ACLs, Bypassing Electronic Locks and Access Controls.This issue affects BlueSpice: from 5.1 through 5.1.3, from 5.2 through 5.2.0. HINT: Versions provided apply to BlueSpice MediaWiki releases. For Extension:NSFileRepo the affected versions are 3.0 < 3.0.5

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

This is an Incorrect Permission Assignment vulnerability in the NSFileRepo extension for BlueSpice MediaWiki. Files or directories have been assigned overly permissive access rights, allowing authenticated users to bypass ACL restrictions and access functionality and resources that should be constrained by access control lists.

MitigationRestrict file and directory permissions in the NSFileRepo extension to enforce proper ACL constraints, ensuring only authorized users can access restricted functionality and resources.

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
Authentication
Y
User interaction
None
Scope
P

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:X/V:X/RE:L/U:X

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 NSFileRepo extension is installed
    Check the BlueSpice MediaWiki extensions directory or the wiki's Special:Version page for the presence of the NSFileRepo extension
    Affected if NSFileRepo extension is listed as installed on the wiki
  2. Locate NSFileRepo files and directories
    Search the webroot for directories or files named 'NSFileRepo', 'nsfilerepo', or containing 'FileRepo' in the extensions folder of the MediaWiki installation
    Affected if NSFileRepo extension files are found in the MediaWiki extensions directory
  3. Check file system permissions on NSFileRepo directories
    Run 'ls -la' or use icacls (Windows) on the NSFileRepo extension directory to inspect read/write/execute permissions for all users or groups
    Affected if Any file or directory within NSFileRepo shows permissions granting broad access (such as 'Everyone', 'Users', or 'Authenticated Users' with modify or full control permissions)
  4. Inspect NSFileRepo configuration files
    Look for and examine any configuration files in the NSFileRepo directory (such as config files, .htaccess, or PHP configuration) to verify permission settings
    Affected if Configuration files exist with permissive access rights or missing ACL enforcement
  5. Test ACL boundary enforcement
    As an authenticated user with limited permissions, attempt to access resources through the NSFileRepo extension that should be restricted by ACLs defined in BlueSpice
    Affected if The restricted resources are accessible to an authenticated user who should not have access according to ACL settings

A user is affected if the NSFileRepo extension is installed and file/directory permissions grant overly broad access that allows authenticated users to bypass intended ACL restrictions.

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

Restrict file and directory permissions in the NSFileRepo extension to enforce proper ACL constraints, ensuring only authorized users can access restricted functionality and resources.

Recommended fix High confidence

NSFileRepo version 3.0.5 or later (BlueSpice MediaWiki 5.1.4+ or 5.2.1+)

  1. 1. Identify the currently installed NSFileRepo extension version in your BlueSpice MediaWiki installation
  2. 2. Navigate to the extensions directory (typically /path/to/mediawiki/extensions/NSFileRepo)
  3. 3. Consult the BlueSpice wiki or repository for the NSFileRepo 3.0.5 release package
  4. 4. Backup your current NSFileRepo extension directory and any related configuration files
  5. 5. Download and replace the existing extension with version 3.0.5 or later
  6. 6. Update any configuration files as needed to match the new version requirements
  7. 7. Clear caches and verify the extension is functioning correctly
  8. 8. Test that file access controls are properly enforced after the upgrade
Caveat Review release notes for any configuration or feature changes between your current version and 3.0.5

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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