How severe is GHSA-rcx7-6m7p-xw5c?

No CVSS score has been assigned to GHSA-rcx7-6m7p-xw5c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rcx7-6m7p-xw5c?

GHSA-rcx7-6m7p-xw5c affects the following packages: ghost (Bitnami). Ecosystems affected: Bitnami.

How do I fix GHSA-rcx7-6m7p-xw5c?

Update ghost to 6.63.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcx7-6m7p-xw5c is resolved across your whole dependency graph.

How do I detect GHSA-rcx7-6m7p-xw5c in my Bitnami dependencies?

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

How do I mitigate GHSA-rcx7-6m7p-xw5c 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-rcx7-6m7p-xw5c actively exploited in the wild?

No public exploit code has been indexed for GHSA-rcx7-6m7p-xw5c 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-rcx7-6m7p-xw5c?

GHSA-rcx7-6m7p-xw5c has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th 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-rcx7-6m7p-xw5c?

GHSA-rcx7-6m7p-xw5c is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rcx7-6m7p-xw5c published, and has it been updated?

GHSA-rcx7-6m7p-xw5c was published on October 9, 2026 and was last updated on October 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Ghost 4.0.0 before 6.63.0 Restricted Content Bypass

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.
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-rcx7-6m7p-xw5c.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

📦ghost

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

Description

Ghost versions from 4.0.0 before 6.63.0 contain a content API vulnerability that allows unauthenticated visitors to access gated post content. Attackers can bypass content restrictions by directly querying the content API to retrieve restricted posts without authentication.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`ghost`	≥ 4.0.0&&< 6.63.0	6.63.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ghost, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ghost to 6.63.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcx7-6m7p-xw5c 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

Ghost versions from 4.0.0 before 6.63.0 contain a content API vulnerability that allows unauthenticated visitors to access gated post content. Attackers can bypass content restrictions by directly querying the content API to retrieve restricted posts without authentication.

O3 Security · Impact-Aware SCA

Is GHSA-rcx7-6m7p-xw5c in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works

Ghost 4.0.0 before 6.63.0 Restricted Content BypassGHSA-rcx7-6m7p-xw5c