How severe is CVE-2017-1000510?

CVE-2017-1000510 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-1000510?

CVE-2017-1000510 affects the following packages: croogo/croogo (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-1000510?

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

How do I detect CVE-2017-1000510 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-2017-1000510 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-2017-1000510 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2017-1000510, 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-2017-1000510?

CVE-2017-1000510 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th 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-2017-1000510?

CVE-2017-1000510 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-2017-1000510 published, and has it been updated?

CVE-2017-1000510 was published on May 14, 2022 and was last updated on February 16, 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

Not in CISA KEV

MEDIUM severity

CVE-2017-1000510 — croogo

MEDIUM

CVE-2017-1000510 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in croogo/croogo. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for croogo/croogo — see the affected versions and patch details below.

Cross site scripting in Croogo

Published

May 14, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% 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

🐘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 version 2.3.1-17-g6f82e6c contains a Cross Site Scripting (XSS) vulnerability in Page name that can result in execution of javascript code.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

croogocroogo

1 version

2.3.1-17-g6f82e6c

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 version 2.3.1-17-g6f82e6c contains a Cross Site Scripting (XSS) v…

github.comNVDFeb 2018

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 4.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000510 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 versions before 4.x contain a Cross Site Scripting (XSS) vulnerability in Page name that can result in execution of javascript code.

O3 Security · Impact-Aware SCA

Is CVE-2017-1000510 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

croogo

2.1/10

Maintained0/10

Code-Review1/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

First exploit

Feb 26, 2018

Disclosed

May 14, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2017-1000510

References

Advisorynvd.nist.gov · CVE 2017 1000510 Webgithub.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-2019-7171CVE-2019-7169CVE-2021-44673

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024