GHSA-9qfv-wgh2-m6p8 — jleehr/canto-saas-api
MEDIUMGHSA-9qfv-wgh2-m6p8 is a medium-severity (CVSS 4.8) vulnerability in jleehr/canto-saas-api. A fix is available for jleehr/canto-saas-api — see the affected versions and patch details below.
canto-saas-api: Authenticated API requests can be redirected via unencoded path variables
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-9qfv-wgh2-m6p8.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-9qfv-wgh2-m6p8 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 374,847 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
jleehr/canto-saas-apiReal-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
Summary
In affected versions, Request::buildRequestUrl() inserts path variables into
the request URL without URL encoding (implode('/', $pathVariables)). All
request classes implementing getPathVariables() are affected, e.g.
GetContentDetailsRequest (scheme, contentId).
If a consuming application passes untrusted input (such as an ID taken from
an HTTP request parameter) as a path variable, characters like ../, ? or
# are sent verbatim and can change the path of the resulting API request.
Impact
An attacker who controls a path variable value can redirect the
library's authenticated request — the Bearer access token is attached in
AbstractEndpoint::sendRequest() — to a different API endpoint of the same
Canto instance, causing unintended reads or writes with the privileges of the
configured app. The impact depends on how the consuming application sources
path variable values; applications that only pass trusted, validated IDs are
not exploitable.
Patches
Fixed in 3.0.0: every path segment is encoded with rawurlencode() before
being inserted into the request URL.
Workarounds
If you cannot upgrade, validate untrusted values before passing them to
request classes, e.g. enforce an allowlist pattern such as
^[A-Za-z0-9_-]+$ for content IDs and schemes.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | jleehr/canto-saas-api | all versions | 3.0.0composer require jleehr/canto-saas-api:^3.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jleehr/canto-saas-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jleehr/canto-saas-api to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9qfv-wgh2-m6p8 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9qfv-wgh2-m6p8 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9qfv-wgh2-m6p8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9qfv-wgh2-m6p8 in your dependencies?
O3 Security finds GHSA-9qfv-wgh2-m6p8 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.