dbcve.org
OctoberApplication · Octobercms

CVE-2026-22692

MEDIUM · 6.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 3.7.13 / 4.1.5 or later.
See remediation →
74/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. Versions prior to 3.7.13 and versions 4.0.0 through 4.1.4 contain a sandbox bypass vulnerability in the optional Twig safe mode feature (CMS_SAFE_MODE). Certain methods on the collect() helper were not properly restricted, allowing authenticated users with template editing permissions to bypass sandbox protections. Exploitation requires authenticated backend access with CMS template editing permissions and only affects installations with CMS_SAFE_MODE enabled (disabled by default). This issue has been fixed in versions 3.7.13 and 4.1.5. To workaround this issue, users can disable CMS_SAFE_MODE if untrusted template editing is not required, and restrict CMS template editing permissions to fully trusted administrators only.

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

October CMS contains a sandbox bypass vulnerability in the optional Twig safe mode feature (CMS_SAFE_MODE) where certain methods on the collect() helper were not properly restricted. Authenticated users with CMS template editing permissions can bypass sandbox protections, potentially executing arbitrary code or accessing sensitive data within the CMS context.

MitigationUpdate to October CMS versions 3.7.13 or 4.1.5. Alternatively, disable CMS_SAFE_MODE if untrusted template editing is not required, or restrict CMS template editing permissions to fully trusted administrators only.

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
OctoberApplication
Affected:< 3.7.13>= 4.0.0, < 4.1.5

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/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. Check October CMS version
    Locate the version file or composer.json in the October CMS installation directory and identify the installed version number.
    Affected if The installed version is below 3.7.13, or is 4.0.0 through 4.1.4.
  2. Verify CMS_SAFE_MODE is enabled
    Inspect the CMS configuration file (typically config/cms.php) or check for the CMS_SAFE_MODE environment variable setting.
    Affected if CMS_SAFE_MODE is set to true or enabled in the configuration.
  3. Confirm CMS template editing permissions exist
    Review backend user roles and permissions in the October CMS administrative panel to identify which users or user groups have template editing capabilities.
    Affected if Non-administrator users or user groups are granted CMS template editing permissions.
  4. Inspect Twig template sandbox configuration
    Examine the Twig environment configuration to verify that sandboxing is active and review which methods on the collect() helper are exposed to template contexts.
    Affected if The sandbox is active but the collect() helper exposes methods that should be restricted under CMS_SAFE_MODE.

You are affected if your October CMS version falls within the vulnerable range AND CMS_SAFE_MODE is enabled AND non-administrator users have template editing permissions.

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 3.7.13 / 4.1.5 or later
Fixed in 3.7.134.1.5
Interim mitigation

Update to October CMS versions 3.7.13 or 4.1.5. Alternatively, disable CMS_SAFE_MODE if untrusted template editing is not required, or restrict CMS template editing permissions to fully trusted administrators only.

Recommended fix High confidence

3.7.13 for 3.x line; 4.1.5 for 4.x line

  1. Backup your October CMS installation and database before making any changes
  2. Identify which major version line you are currently using (3.x or 4.x)
  3. If using 3.x versions (< 3.7.13): Upgrade to version 3.7.13 or later
  4. If using 4.x versions (>= 4.0.0, < 4.1.5): Upgrade to version 4.1.5 or later
  5. After upgrading, verify your CMS_SAFE_MODE configuration matches your security requirements
  6. Test that template editing functionality works correctly after the upgrade

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

Fix this in October Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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