How severe is GHSA-79jw-2f46-wv22?

GHSA-79jw-2f46-wv22 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-79jw-2f46-wv22?

GHSA-79jw-2f46-wv22 affects the following packages: october/system (Packagist), october/system (Packagist), october/system (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-79jw-2f46-wv22?

Update october/system to 1.0.474 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-79jw-2f46-wv22 is resolved across your whole dependency graph.

How do I detect GHSA-79jw-2f46-wv22 in my Packagist dependencies?

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

How do I mitigate GHSA-79jw-2f46-wv22 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-79jw-2f46-wv22 actively exploited in the wild?

No public exploit code has been indexed for GHSA-79jw-2f46-wv22 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-79jw-2f46-wv22?

GHSA-79jw-2f46-wv22 has an EPSS (Exploit Prediction Scoring System) score of 8.6%, placing it in the 95th 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-79jw-2f46-wv22?

GHSA-79jw-2f46-wv22 is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-79jw-2f46-wv22?

A Nuclei detection template exists for GHSA-79jw-2f46-wv22, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-79jw-2f46-wv22 published, and has it been updated?

GHSA-79jw-2f46-wv22 was published on February 23, 2022 and was last updated on February 19, 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

HIGH severity

Authenticated remote code execution in October CMSGHSA-79jw-2f46-wv22

HIGHFix: octobercms/library@c393c5c

GHSA-79jw-2f46-wv22 is a high-severity (CVSS 7.2) CWE-74 vulnerability in october/system. A fix is available for october/system — see the affected versions and patch details below.

Also known asCVE-2022-21705

Published

Feb 23, 2022

Updated

Feb 19, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-79jw-2f46-wv22.

EPSS Exploitation Probability

via FIRST.org ↗

8.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-79jw-2f46-wv22 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

🐘october/system🐘october/system🐘october/system

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

An authenticated user with the permissions to create, modify and delete website pages can exploit this vulnerability to bypass cms.safe_mode / cms.enableSafeMode in order to execute arbitrary code.

This issue only affects admin panels that rely on safe mode and restricted permissions.
To exploit this vulnerability, an attacker must first have access to the backend area.

Patches

The issue has been patched in Build 474 (v1.0.474) and v1.1.10.

Workarounds

Apply https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe to your installation manually if unable to upgrade to Build 474 or v1.1.10.

References

Credits to:

David Miller

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`october/system`	all versions	1.0.474`composer require october/system:^1.0.474`
🐘Packagist	`october/system`	≥ 1.1.0&&< 1.1.10	1.1.10`composer require october/system:^1.1.10`
🐘Packagist	`october/system`	≥ 2.0.0&&< 2.1.27	2.1.27`composer require october/system:^2.1.27`

Affected Products

1 product · 3 configurations

Application

octoberoctobercms

≥ 2.0.0 && < 2.1.27

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/system, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update october/system to 1.0.474 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-79jw-2f46-wv22 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect GHSA-79jw-2f46-wv22

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-79jw-2f46-wv22 -u https://target

Template: October CMS - Remote Code Execution
Severity: high
Impact: Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code on the affected system.
Remediation: The issue has been patched in Build 474 (1.0.474) and 1.1.10. Users unable to upgrade should apply https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe manually to installation.

Template by ProjectDiscovery nuclei-templates (iPhantasmic), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact An authenticated user with the permissions to create, modify and delete website pages can exploit this vulnerability to bypass `cms.safe_mode` / `cms.enableSafeMode` in order to execute arbitrary code. - This issue only affects admin panels that rely on safe mode and restricted permissions. - To exploit this vulnerability, an attacker must first have access to the backend area. ### Patches The issue has been patched in Build 474 (v1.0.474) and v1.1.10. ### Workarounds Apply https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe to your installat