How severe is CVE-2019-20789?

CVE-2019-20789 has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-20789?

CVE-2019-20789 affects the following packages: croogo/croogo (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-20789?

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

How do I detect CVE-2019-20789 in my Packagist dependencies?

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

How do I mitigate CVE-2019-20789 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-2019-20789 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2019-20789, including 1 in-the-wild exploitation 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-2019-20789?

CVE-2019-20789 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th 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-2019-20789?

CVE-2019-20789 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.

When was CVE-2019-20789 published, and has it been updated?

CVE-2019-20789 was published on April 26, 2020 and was last updated on August 7, 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-2019-20789 — croogo

MEDIUM

CVE-2019-20789 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in croogo/croogo. 1 public exploit reference exists, so weaponization risk is real. A fix is available for croogo/croogo — see the affected versions and patch details below.

Croos-site scripting in Croogo

Also known asGHSA-jfvf-rfmq-qwf8

Published

Apr 26, 2020

Updated

Aug 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2019-20789 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐘croogo/croogo

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

Croogo before 3.0.7 allows XSS via the title to admin/menus/menus or admin/taxonomy/vocabularies.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`croogo/croogo`	all versions	3.0.7`composer require croogo/croogo:^3.0.7`

Affected Products

1 product · 1 configurations

Application

croogocroogo

≤ 3.0.6

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.

Croogo before 3.0.7 allows XSS via the title to admin/menus/menus or adm…

github.comNVDApr 2020

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

Croogo before 3.0.7 allows XSS via the title to admin/menus/menus or admin/taxonomy/vocabularies.

O3 Security · Impact-Aware SCA

Is CVE-2019-20789 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

croogo

2.1/10

Code-Review1/10

Maintained0/10

Branch-Protection0/10

Assessed Oct 5, 2026

Timeline

Disclosed

Apr 26, 2020

First exploit

Apr 27, 2020

1 day after disclosure — rapid exploitation

Last updated

Aug 7, 2026

Identifiers

CVE-2019-20789

GHSA-jfvf-rfmq-qwf8

References

Advisorygithub.com Advisorynvd.nist.gov Evidencegithub.com

Related vulnerabilities

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

CVE-2024-42718CVE-2024-29643CVE-2019-7170CVE-2019-7168CVE-2019-7173CVE-2017-1000510CVE-2019-7171CVE-2019-7169

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 7, 2026