How severe is GHSA-wq43-8r5p-w3mc?

No CVSS score has been assigned to GHSA-wq43-8r5p-w3mc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wq43-8r5p-w3mc?

GHSA-wq43-8r5p-w3mc affects the following packages: contao/core (Packagist), contao/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-wq43-8r5p-w3mc?

Update contao/core to 2.11.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wq43-8r5p-w3mc is resolved across your whole dependency graph.

How do I detect GHSA-wq43-8r5p-w3mc in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/core. 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-wq43-8r5p-w3mc 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-wq43-8r5p-w3mc?

O3 pinpoints whether GHSA-wq43-8r5p-w3mc 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-wq43-8r5p-w3mc actively exploited in the wild?

No public exploit code has been indexed for GHSA-wq43-8r5p-w3mc 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-wq43-8r5p-w3mc published, and has it been updated?

GHSA-wq43-8r5p-w3mc was published on May 15, 2024 and was last updated on November 29, 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

GHSA-wq43-8r5p-w3mc

contao/core PHP object injection vulnerability allows for arbitrary code execution

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐘contao/core🐘contao/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

PHP object injection vulnerability was identified in contao/core due to untrusted data being passed to deserialize() function.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`contao/core`	≥ 2.0.0&&< 2.11.14	2.11.14
🐘Packagist	`contao/core`	≥ 3.0.0&&< 3.2.5	3.2.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/core. 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 contao/core to 2.11.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wq43-8r5p-w3mc 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-wq43-8r5p-w3mc 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-wq43-8r5p-w3mc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

PHP object injection vulnerability was identified in contao/core due to untrusted data being passed to `deserialize()` function.

O3 Security · Impact-Aware SCA

Is GHSA-wq43-8r5p-w3mc in your dependencies?

O3 detects GHSA-wq43-8r5p-w3mc across Packagist 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