How severe is CVE-2020-24912?

CVE-2020-24912 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-24912?

CVE-2020-24912 affects the following packages: qcubed/qcubed (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2020-24912?

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

How do I detect CVE-2020-24912 in my Packagist dependencies?

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.

How do I mitigate CVE-2020-24912 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2020-24912 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2020-24912, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-24912?

CVE-2020-24912 has an EPSS (Exploit Prediction Scoring System) score of 6.3%, placing it in the 94th 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 CVE-2020-24912?

CVE-2020-24912 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2020-24912?

A Nuclei detection template exists for CVE-2020-24912, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-24912 published, and has it been updated?

CVE-2020-24912 was published on March 4, 2021 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2020-24912 — qcubed

MEDIUMFix: qcubed/qcubed#1320

CVE-2020-24912 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) 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 reflected cross-site scripting (XSS) vulnerability

Also known asGHSA-xj4v-gp4q-h6qq

Published

Mar 4, 2021

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

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 reflected cross-site scripting (XSS) vulnerability in qcubed (all versions including 3.1.1) in profile.php via the stQuery-parameter allows unauthenticated attackers to steal sessions of authenticated users.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`qcubed/qcubed`	all versions	3.2`composer require qcubed/qcubed:^3.2`

Affected Products

1 product · 1 configurations

Application

qcubedqcubed

≤ 3.1.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A reflected cross-site scripting (XSS) vulnerability in qcubed (all vers…

tech.feedyourhead.atNVDMar 2021

Report on ait.ac.at

ait.ac.atNVDMar 2021

Report on seclists.org

seclists.orgNVDMar 2021

Detection & mitigation playbook

Open-source dependency

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.
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-24912 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

How to detect CVE-2020-24912

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2020-24912 -u https://target

Template: QCube Cross-Site-Scripting
Severity: medium
Impact: Successful exploitation of this vulnerability could allow an attacker to execute malicious scripts in the victim's browser, potentially leading to session hijacking, defacement, or theft of sensitive information.
Remediation: Upgrade to the latest version to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (pikpikcu), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-24912 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

Timeline

Disclosed

Mar 4, 2021

First exploit

Mar 22, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2020-24912

GHSA-xj4v-gp4q-h6qq

References

Advisorynvd.nist.gov · CVE 2020 24912 Fixtech.feedyourhead.at · QCubed Cross Site Scripting CVE 2020 24912 Fixait.ac.at · ait sa 20210215 03 Webpacketstormsecurity.com · QCubed 3.1.1 Cross Site Scripting Webgithub.com · files Webqcubed.com Packagegithub.com · qcubed Evidenceseclists.org

Related vulnerabilities

Also affects qcubed/qcubed

This CVE is medium severity; 2 of 2 other CVEs affecting qcubed/qcubed are rated as high or higher (top: critical).

CVE-2020-24914CVE-2020-24913

Same weakness: CWE-79

This CVE is medium severity; 4 of 6 other CVEs with CWE-79 are rated as high or higher (top: high).

CVE-2026-126075CVE-2026-126063CVE-2026-110802CVE-2026-123364CVE-2026-118670CVE-2026-88986Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026