How severe is GHSA-gqpw-9q54-9x28?

No CVSS score has been assigned to GHSA-gqpw-9q54-9x28 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gqpw-9q54-9x28?

GHSA-gqpw-9q54-9x28 affects the following packages: concrete5/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-gqpw-9q54-9x28?

Update concrete5/core to 8.5.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqpw-9q54-9x28 is resolved across your whole dependency graph.

How do I detect GHSA-gqpw-9q54-9x28 in my Packagist dependencies?

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

How do I mitigate GHSA-gqpw-9q54-9x28 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-gqpw-9q54-9x28 actively exploited in the wild?

No public exploit code has been indexed for GHSA-gqpw-9q54-9x28 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-gqpw-9q54-9x28?

GHSA-gqpw-9q54-9x28 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th 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-gqpw-9q54-9x28?

GHSA-gqpw-9q54-9x28 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-gqpw-9q54-9x28 published, and has it been updated?

GHSA-gqpw-9q54-9x28 was published on November 23, 2021 and was last updated on December 2, 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

Server-Side Request Forgery in Concrete CMSGHSA-gqpw-9q54-9x28

GHSA-gqpw-9q54-9x28 is a Server-Side Request Forgery (SSRF) vulnerability in concrete5/core. A fix is available for concrete5/core — see the affected versions and patch details below.

Also known asCVE-2021-22970

Published

Nov 23, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘concrete5/core

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

Concrete CMS (formerly concrete5) versions 8.5.6 and below and version 9.0.0 allow local IP importing causing the system to be vulnerable toa. SSRF attacks on the private LAN servers by reading files from the local LAN. An attacker can pivot in the private LAN and exploit local network appsandb. SSRF Mitigation Bypass through DNS RebindingConcrete CMS security team gave this a CVSS score of 3.5 AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:NConcrete CMS is maintaining Concrete version 8.5.x until 1 May 2022 for security fixes.This CVE is shared with HackerOne Reports https://hackerone.com/reports/1364797 and https://hackerone.com/reports/1360016Reporters: Adrian Tiron from FORTBRIDGE (https://www.fortbridge.co.uk/ ) and Bipul Jaiswal

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`concrete5/core`	all versions	8.5.7`composer require concrete5/core:^8.5.7`

Affected Products

1 product · 2 configurations

Application

concrete cmsconcretecms

≤ 8.5.6

1 version

9.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for concrete5/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update concrete5/core to 8.5.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqpw-9q54-9x28 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

Concrete CMS (formerly concrete5) versions 8.5.6 and below and version 9.0.0 allow local IP importing causing the system to be vulnerable to SSRF attacks on the private LAN to servers by reading files from the local LAN. An attacker can pivot in the private LAN and exploit local network appsandb.

O3 Security · Impact-Aware SCA

Is GHSA-gqpw-9q54-9x28 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works