How severe is GHSA-qc57-h2f7-p4hx?

GHSA-qc57-h2f7-p4hx has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qc57-h2f7-p4hx?

GHSA-qc57-h2f7-p4hx affects the following packages: plone (PyPI), plone (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-qc57-h2f7-p4hx?

Update plone to 4.3.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qc57-h2f7-p4hx is resolved across your whole dependency graph.

How do I detect GHSA-qc57-h2f7-p4hx in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone. 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.

How do I mitigate GHSA-qc57-h2f7-p4hx 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.

How does O3 Security protect against GHSA-qc57-h2f7-p4hx?

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

Is GHSA-qc57-h2f7-p4hx actively exploited in the wild?

No public exploit code has been indexed for GHSA-qc57-h2f7-p4hx 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.

When was GHSA-qc57-h2f7-p4hx published, and has it been updated?

GHSA-qc57-h2f7-p4hx was published on May 13, 2022 and was last updated on October 18, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-qc57-h2f7-p4hx

MEDIUM

GHSA-qc57-h2f7-p4hx is a medium-severity (CVSS 6.5) vulnerability in plone. O3 Security confirms whether GHSA-qc57-h2f7-p4hx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Plone Unauthorized Access Vulnerability

Also known asCVE-2017-1000483PYSEC-2018-72

Published

May 13, 2022

Updated

Oct 18, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐍plone🐍plone

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

Description

Accessing private content via str.format in through-the-web templates and scripts in Plone 2.5-5.1rc1. This improves an earlier hotfix. Since the format method was introduced in Python 2.6, this part of the hotfix is only relevant for Plone 4 and 5.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`plone`	≥ 2.5&&< 4.3.16	4.3.16
🐍PyPI	`plone`	≥ 5.0&&< 5.1.0	5.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone. 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.
Fix
Update plone to 4.3.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qc57-h2f7-p4hx 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 O3 protects you
O3 pinpoints whether GHSA-qc57-h2f7-p4hx 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-qc57-h2f7-p4hx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Accessing private content via `str.format` in through-the-web templates and scripts in Plone 2.5-5.1rc1. This improves an earlier hotfix. Since the format method was introduced in Python 2.6, this part of the hotfix is only relevant for Plone 4 and 5.

O3 Security · Impact-Aware SCA

Is GHSA-qc57-h2f7-p4hx in your dependencies?

O3 detects GHSA-qc57-h2f7-p4hx across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works