NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
CRITICAL severity

LavaLite vulnerable to web cache poisoningGHSA-6vcf-cfjp-qxcw

CRITICAL

GHSA-6vcf-cfjp-qxcw is a critical-severity (CVSS 9.8) CWE-444 vulnerability in lavalite/cms. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2023-27238
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • 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-6vcf-cfjp-qxcw.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk
0.37%0.70%1.03%1.37%0.9%0.9%0.9%Jul 26Sep 26Nov 26

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

1 pkg affected
🐘lavalite/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

LavaLite CMS v 9.0.0 was discovered to be vulnerable to web cache poisoning.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐘Packagistlavalite/cmsall versionsNo fix

Affected Products

1 product · 1 configurations
Application
lavalitelavalite
1 version
9.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Remediation status

    The records we use list no patched version of lavalite/cms for GHSA-6vcf-cfjp-qxcw. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  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.

Frequently Asked Questions

LavaLite CMS v 9.0.0 was discovered to be vulnerable to web cache poisoning.
O3 Security · Impact-Aware SCA

Is GHSA-6vcf-cfjp-qxcw in your dependencies?

Find it across Packagist, including transitive dependencies.

LavaLite vulnerable to web cache poisoning (Critical 9.8)