Approved changes feed: RSS · Atom
cpe:2.3:a:octobercms:october:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Octobercms (50ac530a-7544-5bf4-b757-db1aeff0e595) |
|---|---|
| Product | October (51c55d07-6379-53f0-b3f3-ef5e6285377e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-49400 |
vulnerable | 2026-10-13 12:28:44.334962 |
October CMS: PHP Object Injection via Backend Widget Session Storage
LOW (3.3)
October System provides the system module for October Content Management System. Prior to versions 3.7.17 and 4.2.21, the backend `SessionMaker` trait stored widget session state as `base64(serialize(...))` and consumed it with `unserialize()` without an `allowed_classes` restriction. Any code path that could write to a `widget.*` session key with attacker-controlled bytes could trigger PHP object injection the next time the widget read its session state, allowing instantiation of arbitrary classes and reachable PHP gadget chains. This issue only affects installations running with `cms.safe_mode` enabled. Safe Mode is a niche opt-in feature, primarily used for demo installations and multi-tenant or shared-editor scenarios where untrusted users are deliberately granted access to the CMS markup editor. In standard production deployments Safe Mode is off, backend access is restricted to trusted administrators, and a markup editor can already execute arbitrary PHP directly. The session-write path that reaches this sink is gated by the Safe Mode sandbox, so installations without Safe Mode enabled are not exposed. Scope of impact is narrow even with Safe Mode enabled. The standard backend code paths that populate widget session state (search terms, sort options, selected IDs, filter values) wrap the input inside a known array shape before serializing, so user-supplied values never reach `unserialize()` as a controllable serialized payload. Exploitation requires the Safe Mode session-write path together with a suitable PHP gadget chain reachable from the installed dependency set. The hardening below removes the underlying object-injection sink so the class of issue is closed off regardless. The vulnerability has been patched in v3.7.17 and v4.2.21. Two changes were applied. `Backend\Traits\SessionMaker` now stores widget session state as plain JSON instead of `base64(serialize(...))`, eliminating the object-injection sink entirely for new writes. Reads transparently fall back to the legacy format for one upgrade cycle so existing sessions retain their saved widget state. The legacy `unserialize()` fallback path now sets `allowed_classes => false`, so even values written before the upgrade cannot instantiate objects. As a workaround, restrict CMS markup editing access to fully trusted administrators only, the standard October CMS recommendation for any deployment.
Published: 2026-09-14T17:15:12.881Z
Updated: 2026-09-16T15:21:15.863Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-29179 |
vulnerable | 2026-06-08 07:55:16.183598 |
October: Editor Sub-Permission Bypass for Asset and Blueprint File Operations
LOW (3.3)
October is a Content Management System (CMS) and web platform. Prior to 3.7.16 and 4.1.16, fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted editor access but had editor.cms_assets or editor.tailor_blueprints specifically withheld, an uncommon permission configuration. In this edge case, such users could perform file operations (create, delete, rename, move, upload) on theme assets or blueprint files despite lacking the required sub-permission. A related operator precedence error in the Tailor navigation also disclosed the theme blueprint directory tree under the same conditions. This vulnerability is fixed in 3.7.16 and 4.1.16.
Published: 2026-04-21T16:19:52.447Z
Updated: 2026-04-21T16:46:47.873Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27937 |
vulnerable | 2026-06-08 07:55:14.677901 |
October: Reflected XSS via DataTable Form Widget
LOW (3.1)
October is a Content Management System (CMS) and web platform. Prior to 3.7.16 and 4.1.16, a reflected Cross-Site Scripting (XSS) vulnerability was identified in the backend DataTable widget where a query parameter was rendered without proper output escaping. This vulnerability is fixed in 3.7.16 and 4.1.16.
Published: 2026-04-21T16:17:06.973Z
Updated: 2026-04-21T20:37:33.620Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-26274 |
vulnerable | 2026-06-08 07:53:21.461892 |
October: Safe Mode Bypass via Twig Database Write Operations
MEDIUM (6.6)
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.
Published: 2026-04-21T16:16:06.488Z
Updated: 2026-04-21T19:16:38.739Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-26067 |
vulnerable | 2026-06-08 07:53:20.766639 |
October: Safe Mode Bypass via CSS Preprocessor Compilers
MEDIUM (4.9)
October is a Content Management System (CMS) and web platform. Prior to 3.7.14 and 4.1.10, a server-side information disclosure vulnerability was identified in the handling of CSS preprocessor files. Backend users with Editor permissions could craft .less, .sass, or .scss files that leverage the compiler's import functionality to read arbitrary files from the server. This worked even with cms.safe_mode enabled. This vulnerability is fixed in 3.7.14 and 4.1.10.
Published: 2026-04-21T16:16:03.293Z
Updated: 2026-04-21T17:35:19.882Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25133 |
vulnerable | 2026-06-08 07:53:19.031455 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25125 |
vulnerable | 2026-06-08 07:53:19.023386 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-24907 |
vulnerable | 2026-06-08 07:53:18.664747 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-24906 |
vulnerable | 2026-06-08 07:53:18.664292 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22692 |
vulnerable | 2026-06-08 07:51:13.607326 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-61676 |
vulnerable | 2026-06-08 07:37:27.916448 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-61674 |
vulnerable | 2026-06-08 07:37:27.914851 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-51991 |
vulnerable | 2026-06-08 06:52:14.557409 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-25837 |
vulnerable | 2026-06-08 06:31:23.892126 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-25637 |
vulnerable | 2026-06-08 06:31:23.630452 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-24764 |
vulnerable | 2026-06-08 06:29:41.687278 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-44383 |
vulnerable | 2026-06-08 06:12:40.869337 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-44382 |
vulnerable | 2026-06-08 06:12:40.868873 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-44381 |
vulnerable | 2026-06-08 06:12:40.867947 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-35944 |
vulnerable | 2026-06-08 05:46:06.037162 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24800 |
vulnerable | 2026-06-08 05:41:01.714705 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23655 |
vulnerable | 2026-06-08 05:40:58.134333 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-21705 |
vulnerable | 2026-06-08 05:40:02.049655 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-41126 |
vulnerable | 2026-06-08 05:35:19.785780 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3311 |
vulnerable | 2026-06-08 05:33:51.153778 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32650 |
vulnerable | 2026-06-08 05:32:07.771395 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32649 |
vulnerable | 2026-06-08 05:32:07.770908 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32648 |
vulnerable | 2026-06-08 05:32:07.769454 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-29487 |
vulnerable | 2026-06-08 05:31:26.451795 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21265 |
vulnerable | 2026-06-08 05:29:11.477878 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21264 |
vulnerable | 2026-06-08 05:29:11.477459 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-5299 |
vulnerable | 2026-06-08 05:26:41.687410 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-5298 |
vulnerable | 2026-06-08 05:26:41.686842 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-5297 |
vulnerable | 2026-06-08 05:26:41.686453 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-5296 |
vulnerable | 2026-06-08 05:26:41.685959 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-5295 |
vulnerable | 2026-06-08 05:26:41.685495 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-4061 |
vulnerable | 2026-06-08 05:25:58.796873 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-26231 |
vulnerable | 2026-06-08 05:23:50.922815 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-15249 |
vulnerable | 2026-06-08 05:19:25.585159 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-15248 |
vulnerable | 2026-06-08 05:19:25.584815 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-15247 |
vulnerable | 2026-06-08 05:19:25.584464 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-15246 |
vulnerable | 2026-06-08 05:19:25.583918 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-15128 |
vulnerable | 2026-06-08 05:19:25.325558 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-11083 |
vulnerable | 2026-06-08 05:16:36.427552 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-7198 |
vulnerable | 2026-06-08 05:11:55.161331 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-1999008 |
vulnerable | 2026-06-08 05:11:15.086724 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-16941 |
vulnerable | 2026-06-08 05:09:07.604866 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-1000197 |
vulnerable | 2026-06-08 05:08:34.233409 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-1000196 |
vulnerable | 2026-06-08 05:08:34.233133 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-1000195 |
vulnerable | 2026-06-08 05:08:34.232860 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-1000194 |
vulnerable | 2026-06-08 05:08:34.232570 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-1000193 |
vulnerable | 2026-06-08 05:08:34.232202 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.