Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
CRITICAL severity

GHSA-gc45-j3m5-8qfq

CRITICALFix: liufee/cms@d45cb9c

GHSA-gc45-j3m5-8qfq is a critical-severity (CVSS 9.1) Server-Side Request Forgery (SSRF) vulnerability in feehi/cms. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-gc45-j3m5-8qfq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Server-Side Request Forgery in Feehi CMS

Also known asCVE-2021-30108
Published
Jun 8, 2021
Updated
Feb 16, 2024
Affected
1 pkg
Patched
None yet
Exploits
1 known
Exploitation data as of Feb 16, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘feehi/cms

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

Feehi CMS 2.1.1 is affected by a Server-side request forgery (SSRF) vulnerability. When the user modifies the HTTP Referer header to any url, the server can make a request to it.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐘Packagistfeehi/cmsall versionsNo fix
Exploits & PoCs
1

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for feehi/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of feehi/cms has shipped for GHSA-gc45-j3m5-8qfq yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-gc45-j3m5-8qfq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gc45-j3m5-8qfq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Feehi CMS 2.1.1 is affected by a Server-side request forgery (SSRF) vulnerability. When the user modifies the HTTP Referer header to any url, the server can make a request to it.
O3 Security · Impact-Aware SCA

Is GHSA-gc45-j3m5-8qfq in your dependencies?

O3 detects GHSA-gc45-j3m5-8qfq across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.