How severe is GHSA-7ggw-h8pp-r95r?

GHSA-7ggw-h8pp-r95r has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-7ggw-h8pp-r95r?

GHSA-7ggw-h8pp-r95r affects the following packages: october/rain (Packagist), october/rain (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-7ggw-h8pp-r95r?

Update october/rain to 1.0.472 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7ggw-h8pp-r95r is resolved across your whole dependency graph.

How do I detect GHSA-7ggw-h8pp-r95r in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/rain, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-7ggw-h8pp-r95r if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-7ggw-h8pp-r95r actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-7ggw-h8pp-r95r, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-7ggw-h8pp-r95r?

GHSA-7ggw-h8pp-r95r has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-7ggw-h8pp-r95r?

GHSA-7ggw-h8pp-r95r is classified as CWE-613 (CWE-613). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7ggw-h8pp-r95r published, and has it been updated?

GHSA-7ggw-h8pp-r95r was published on February 10, 2021 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

October CMS Session ID not invalidated after logoutGHSA-7ggw-h8pp-r95r

CRITICALFix: octobercms/library@642f597

GHSA-7ggw-h8pp-r95r is a critical-severity (CVSS 9.8) CWE-613 vulnerability in october/rain. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for october/rain — see the affected versions and patch details below.

Also known asCVE-2021-3311

Published

Feb 10, 2021

Updated

Feb 16, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘october/rain🐘october/rain

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

When logging out, the session ID was not invalidated. This is not a problem while the user is logged out, but as soon as the user logs back in the old session ID would be valid again; which means that anyone that gained access to the old session cookie would be able to act as the logged in user. This is not a major concern for the majority of cases, since it requires a malicious party gaining access to the session cookie in the first place, but nevertheless has been fixed.

Patches

Issue has been patched in Build 472 (v1.0.472) and v1.1.2.

Workarounds

Apply https://github.com/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024 to your installation manually if unable to upgrade to Build 472 or v1.1.2.

References

Reported by Anisio (Brazilian Information Security Analyst)
http://cve.circl.lu/cve/CVE-2021-3311

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Threat assessment:

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`october/rain`	all versions	1.0.472`composer require october/rain:^1.0.472`
🐘Packagist	`october/rain`	≥ 1.1.0&&< 1.1.2	1.1.2`composer require october/rain:^1.1.2`

Affected Products

1 product · 1 configurations

Application

octoberoctobercms

≤ 1.0.471

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in October through build 471. It reactivates an …

anisiosantos.meNVDMar 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/rain, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update october/rain to 1.0.472 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7ggw-h8pp-r95r is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact When logging out, the session ID was not invalidated. This is not a problem while the user is logged out, but as soon as the user logs back in the old session ID would be valid again; which means that anyone that gained access to the old session cookie would be able to act as the logged in user. This is not a major concern for the majority of cases, since it requires a malicious party gaining access to the session cookie in the first place, but nevertheless has been fixed. ### Patches Issue has been patched in Build 472 (v1.0.472) and v1.1.2. ### Workarounds Apply https://github.c