dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-38329

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Bludit CMS before version 3.18.4 allows Remote Code Execution (RCE) via the API Plugin. The POST /api/files/{key} endpoint in bl-plugins/api/plugin.php fails to perform authorization checks and lacks file extension validation. An attacker with a valid API token can upload a malicious PHP script and execute arbitrary code on the server.

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

Bludit CMS before 3.18.4 has an RCE vulnerability in the API plugin where the POST /api/files/{key} endpoint lacks authorization checks and file extension validation. An attacker with a valid API token can upload a malicious PHP script to achieve remote code execution.

MitigationUpgrade to Bludit CMS version 3.18.4 or later which includes proper authorization checks and file extension validation. If the API is not required, disable the API plugin as a temporary mitigation.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Bludit CMS installation
    Locate the Bludit installation directory - look for the 'bl-content' folder or typical web root paths like /var/www/html/bludit, /www/bludit, or C:\inetpub\bludit
    Affected if Bludit CMS is installed on the system
  2. Determine Bludit version
    Check the version file - in Bludit, the version is typically stored in a 'version.php' or 'bl-version' file in the root directory or in the 'bl-system' folder. Read the file to extract the version number
    Affected if The installed version is earlier than 3.18.4 (e.g., 3.18.3, 3.18.0, etc.)
  3. Verify API plugin is enabled
    Check the plugins directory configuration - look in the 'bl-plugins' folder for an 'api' or 'API' subdirectory. Also check bl-content/databases/plugins.php to see if the API plugin is listed as enabled
    Affected if The API plugin folder exists and the plugin is enabled in the configuration
  4. Confirm API token is configured
    Check for API token configuration - look in bl-content/databases/ for files related to API authentication (commonly api.php or similar), or check the API plugin's configuration file in bl-plugins/api/
    Affected if An active API token exists in the Bludit configuration

All conditions must be met: Bludit CMS is installed, version is before 3.18.4, the API plugin is enabled, and an API token is configured - if all are true, the environment is vulnerable to CVE-2026-38329

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 to Bludit CMS version 3.18.4 or later which includes proper authorization checks and file extension validation. If the API is not required, disable the API plugin as a temporary mitigation.

Recommended fix High confidence

Bludit CMS version 3.18.4 or later

  1. 1. Backup your Bludit CMS installation and database before making any changes.
  2. 2. Download Bludit CMS version 3.18.4 or later from the official repository (github.com/bludit/bludit)
  3. 3. Replace the existing files with the new version, preserving your content directory (bl-content) and configuration
  4. 4. Verify the API plugin has been updated to the patched version
  5. 5. Test that the /api/files/{key} endpoint now properly performs authorization checks
  6. 6. Ensure your API tokens are still valid and functioning correctly after the upgrade
Caveat Review custom configurations and plugins for compatibility with the new version before deploying to production

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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