CriticalCVE-2021-32648

    Account Takeover in Octobercms (CVE-2021-32648)

    Published In CISA KEV since Sources: CVE.org, OSV

    Share

    What is affected, what to do

    octobercms in a CMS platform based on the Laravel PHP Framework. In affected versions of the october/system package an attacker can request an account password reset and then gain access to the account using a specially crafted request.

    The vulnerability is being actively exploited; treat it as a priority. Update october to version 1.1.5. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • October CMS gte 1.0.471, < 1.0.472..*

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.1

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    8.2

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org, OSV

    91.2 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.81

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    220.70 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.2
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    91.2 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.81
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 6 February 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-287

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This CVE is on KEV because it is remotely exploitable without authentication and hands the attacker a backend admin account — which in October CMS effectively means remote code execution, since admins have access to the built-in PHP code editor and file uploads. Exploitation likelihood sits in the very top tier of all known CVEs and public PoCs have been circulating since 2021. Typical targets are public-facing marketing, association and public-sector sites running October CMS; treat every internet-exposed instance as P1 and segmented internal instances as P2. For NIS2-scoped operators a compromised CMS instance is routinely a reportable incident once it can be used as a pivot into the internal network.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Upgrade October CMS to Build 472 (1.0.x branch) or version 1.1.5 or later without delay; via Composer: composer update october/system followed by php artisan october:up.
      • Temporarily lock all backend accounts (admins first) or force a password rotation until the upgrade is verified — any prior reset flow may have been abused.
      • Restrict the backend URL (/backend or your customised path) to an IP allowlist, VPN, or reverse-proxy auth (Basic Auth, mTLS) to remove it from the public internet.
      • Review mail logs and the backend_users table for anomalous password-reset activity over the last 90 days; disable suspect accounts and invalidate rows in the sessions table.
      • After patching, rotate all API tokens, persistent-login cookies and session keys (APP_KEY in .env), as a successful intruder may already have exfiltrated secrets.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: expose the backend path only to the admin network via WAF/reverse proxy; keep the public internet limited to the frontend site.
      • WAF rule: inspect POST requests to /backend/auth/reset/* and /backend/auth/restore for abnormal parameter shapes (tampered code parameter, overly structured reset tokens, repeated resets per source IP) and block.
      • Rate-limit /backend/auth/* (e.g. Nginx limit_req or Cloudflare rule) to roughly 5 requests per minute per source IP.
      • IAM hardening: enforce two-factor authentication for every backend user (via rainlab/user plugin or equivalent); apply least privilege, specifically stripping file-upload and code-editor permissions from non-essential roles.
      • Configuration: enable cms.enableSafeMode = true and cms.disableCoreUpdates to prevent PHP code execution through the backend editor — this limits blast radius if an account is compromised.
      • Monitoring: deploy file-integrity monitoring (AIDE, Wazuh) across plugins/, themes/ and storage/cms/ to catch follow-on webshell drops.
    3. Runbook step 3

      Detection rules

      • Web access log: multiple POST requests to /backend/auth/restore or /backend/auth/reset from the same source IP in a short window — Sigma: selection: cs-uri-stem|contains: '/backend/auth/reset' with count() by src_ip > 5 in 10m.
      • Application log/DB: rows in backend_users with an updated reset_password_code without a preceding user-initiated flow; correlate SQL audit on UPDATE backend_users SET password with the absence of a legitimate login event.
      • Mail gateway: outbound password-reset emails from the October instance to unexpected or external recipient domains — alert when the recipient is not on the known admin roster.
      • EDR/Sysmon on the web server: php-fpm or www-data spawning sh, bash, python, curl, wget — Sysmon EID 1 where ParentImage ends in php* and Image is a shell/interpreter.
      • FIM alert on new or modified .php files under storage/cms/cache/, plugins/*/components/ or themes/*/ outside scheduled deployment windows.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    octobercms in a CMS platform based on the Laravel PHP Framework. In affected versions of the october/system package an attacker can request an account password reset and then gain access to the account using a specially crafted request. The issue has been patched in Build 472 and v1.1.5.

    Source: NVD (NIST), OSV (Open Source Vulnerabilities), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    octobercmsoctober
    • ≥ 1.0.471, < 1.0.472
    • 1.0.471
    • 1.1.1 – < 1.1.5
    • —
    • —
    • 1.1.5
    packagistoctober/system
    • v1.0.364
    • v1.0.452
    • v1.0.402
    • v1.0.427
    • v1.0.347
    • v1.0.434
    • v1.0.353
    • v1.0.346
    • v1.0.391
    • v1.0.467
    • v1.0.414
    • v1.0.378
    • v1.0.367
    • v1.0.355
    • v1.0.404
    • v1.0.369
    • v1.0.371
    • v1.0.379
    • v1.0.437
    • v1.0.447
    • v1.0.408
    • v1.0.359
    • v1.0.468
    • v1.1.2
    • v1.0.399
    • v1.0.387
    • v1.0.340
    • v1.0.454
    • v1.0.435
    • v1.0.392
    • v1.0.331
    • v1.0.323
    • v1.0.393
    • v1.0.385
    • v1.0.368
    • v1.0.444
    • v1.0.461
    • v1.0.333
    • v1.0.395
    • 1.1.1
    • v1.0.425
    • v1.0.390
    • v1.0.327
    • v1.0.410
    • v1.0.456
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-287Improper Authentication

      Class

      When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

      Entry at MITRE CWE-287

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • github.comoctobercms/october/security/advisories/GHSA-mxr5-mc97-63rcweb, x_refsource_CONFIRM, Patch, Vendor advisory
    • NVD (NIST)vuln/detail/CVE-2021-32648advisory
    • github.comoctobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9…web, x_refsource_MISC, Patch
    • github.comoctobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de…web, x_refsource_MISC, Patch
    • github.comoctobercms/octoberpackage
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2021-32648web, government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2021-32648
    <a href="https://intel.neosec.eu/en/cve/CVE-2021-32648"><img src="https://intel.neosec.eu/badge/cve/CVE-2021-32648.svg?lang=en" alt="CVE-2021-32648 – NEOSEC Intel" height="20"></a>