dbcve.org
CWE-184Weakness · CWE-184

CVE-2026-26274

MEDIUM · 6.6 CVSS v3.1 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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
October is a Content Management System (CMS) and web platform. Prior to 3.7.14 and 4.1.10, a vulnerability was identified in the Twig sandbox security policy that allowed database write operations when cms.safe_mode is enabled. Backend users with Developer permissions could use Twig template markup to execute insert, update, and delete operations on any database table through the query builder, which is included in the sandbox allow-list. This vulnerability is fixed in 3.7.14 and 4.1.10.

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

A Twig sandbox security policy bypass in October CMS allowed database write operations (insert, update, delete) when cms.safe_mode was enabled. The query builder was incorrectly included in the sandbox allow-list, enabling Developer-level backend users to execute arbitrary database operations through Twig template markup on any table.

MitigationUpgrade to October CMS version 3.7.14 or 4.1.10 or later to patch the vulnerability. If immediate patching is not feasible, revoke Developer-level backend permissions until the update can be applied.

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

CVSS:3.1/AV:N/AC:H/PR:H/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. Determine October CMS version
    Check the composer.json file in the October CMS root directory, or look for a version constant in the system classes. Alternatively, check the backend system settings page for the installed CMS version.
    Affected if Version is before 3.7.14 or 4.1.10 (any version prior to the patched releases)
  2. Verify cms.safe_mode configuration
    Examine the CMS configuration file (typically config/cms.php or config/backend.php) and look for the 'safe_mode' setting, or check the CMS settings in the backend administrative panel.
    Affected if cms.safe_mode is set to true or enabled in the configuration
  3. Identify Developer-level backend users
    Access the backend Users panel and filter for users with the Developer role, or query the backend_users table in the database for users with the role_id corresponding to Developer permissions.
    Affected if At least one backend user with Developer-level permissions exists in the system
  4. Confirm query builder accessibility in Twig sandbox
    Inspect the Twig sandbox configuration or service provider to verify whether the query builder or database builder is included in the allowed methods list. This may require reviewing vendor files or configuration that defines sandboxed functions.
    Affected if The query builder/database builder is present in the Twig sandbox allow-list when safe_mode is active

You are affected if running October CMS version before 3.7.14 or 4.1.10, with cms.safe_mode enabled, and having at least one Developer-level backend user account.

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 October CMS version 3.7.14 or 4.1.10 or later to patch the vulnerability. If immediate patching is not feasible, revoke Developer-level backend permissions until the update can be applied.

Recommended fix High confidence

October CMS 3.7.14 (for 3.x branch) or 4.1.10 (for 4.x branch)

  1. Backup your October CMS installation and database before proceeding
  2. Identify your current October CMS version by checking the version file or admin panel
  3. If running October CMS 3.x branch, upgrade to version 3.7.14 or later
  4. If running October CMS 4.x branch, upgrade to version 4.1.10 or later
  5. Update via composer: `composer update october/system --no-interaction` or use the admin panel update function
  6. Clear cache after upgrade: `php artisan cache:clear`
  7. Verify the upgrade was successful by checking the version number
  8. Test that cms.safe_mode functions correctly with the new version
Caveat Review October CMS release notes for any breaking changes between your current version and the target version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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