Reliance on Cookies without validation in OctoberCMS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N

EPSS

• CVE-2020-15128: 0.69% estimated exploitation activity in the next 30 days; percentile 52.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Previously encrypted cookie values were not tied to the name of the cookie the value belonged to. This meant that certain classes of attacks that took advantage of other theoretical vulnerabilities in user facing code (nothing exploitable in the core project itself) had a higher chance of succeeding. Specifically, if your usage exposed a way for users to provide unfiltered user input and have it returned to them as an encrypted cookie (ex. storing a user provided search query in a cookie) they could then use the generated cookie in place of other more tightly controlled cookies; or if your usage exposed the plaintext version of an encrypted cookie at any point to the user they could theoretically provide encrypted content from your application back to it as an encrypted cookie and force the framework to decrypt it for them. Patches Issue has been patched in Build 468 (v1.0.468). NOTE: If you are using the cookie session driver, all of your session data will be invalidated. All…

Published by the source

5 Aug 2020, 14:52 UTC

Last modified by the source

1 Feb 2023, 05:04 UTC

Source last checked

26 Oct 2026, 14:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-55mm-5399-7r63

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-15128

Advisory: Reliance on Cookies without validation in OctoberCMS
IDs: CVE-2020-15128, GHSA-55mm-5399-7r63
Record: https://patchnext.com/advisories/cve-2020-15128 (revision 1, source checked 26 Oct 2026, 14:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: october/rain 1.0.468. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist october/rain: affected >= 1.0.319, < 1.0.468; fixed in 1.0.468

## Suggested inspection (read-only)
- Packagist october/rain: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on october/rain.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-55mm-5399-7r63 (GitHub-reviewed advisory GHSA-55mm-5399-7r63 lists affected ranges: Packagist october/rain >=1.0.319 <1.0.468)

Commands are suggestions: review each one before running it.