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

CVE-2020-24914 — qcubed

CRITICALFix: qcubed/qcubed#1320

CVE-2020-24914 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in qcubed/qcubed. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for qcubed/qcubed — see the affected versions and patch details below.

qcubed PHP object injection

Also known asGHSA-7w3c-jgh7-cwjw
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
5.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk
0.00%15.8%31.7%47.5%37.7%5.0%May 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
🐘qcubed/qcubed

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

A PHP object injection bug in profile.php in qcubed (all versions including 3.1.1) unserializes the untrusted data of the POST-variable "strProfileData" and allows an unauthenticated attacker to execute code via a crafted POST request.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistqcubed/qcubedall versions3.2composer require qcubed/qcubed:^3.2

Affected Products

1 product · 1 configurations
Application
qcubedqcubed
≤ 3.1.1
range
Exploits & PoCs
3

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 qcubed/qcubed, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update qcubed/qcubed to 3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-24914 is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

A PHP object injection bug in profile.php in qcubed (all versions including 3.1.1) unserializes the untrusted data of the POST-variable "strProfileData" and allows an unauthenticated attacker to execute code via a crafted POST request.
O3 Security · Impact-Aware SCA

Is CVE-2020-24914 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2020-24914: qcubed — Fixed in 3.2