Lack of Input Validation in zendesk_api_client_php for Zendesk Subdomain
CVE-2021-30492
CRITICALCVSS · not yet scored
Also known asGHSA-q348-f93x-9gx4 (GitHub Security Advisories)
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: —CVSS v2: —Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS
- —
- EchelonGraph score
- Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
- EG Severity
- Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
- EG Likelihood
- Unknown (no EPSS on record)Unknown, not low: FIRST has published no EPSS probability for this CVE.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
April 29, 2021
Last Modified
April 29, 2021
Vendor Advisories for CVE-2021-30492(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| composer | zendesk/zendesk_api_client_php @ 2.2.11 (fixes < 2.2.11) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| zendesk/zendesk_api_client_php | 2.0.0-beta ... v2.2.9 (37 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 0× in last 7d / 1× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-03 19:33 UTCEchelonGraph re-scored
- 2026-11-03 19:33 UTCGHSA enrichmentGHSA-q348-f93x-9gx4 · GitHub severity CRITICAL
Related CVEs(same CWE)
Frequently asked(3)
What is CVE-2021-30492?
CVE-2021-30492 is a critical-severity vulnerability; its CVE record was published on April 29, 2021. Lack of Input Validation in zendesk_api_client_php for Zendesk Subdomain Impact Lack of input validation of the Zendesk subdomain could expose users of the library to Server Side Request Forgery (SSRF). Resolution Validate the provided Zendesk subdomain to be a valid subdomain in: getAuthUrl…
When was the CVE record for CVE-2021-30492 published?
The CVE record for CVE-2021-30492 was published on April 29, 2021. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 29, 2021; the record at its source may have been updated since.
How do I remediate CVE-2021-30492?
A fix for CVE-2021-30492 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-30492 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-30492
Is Your Infrastructure Affected by CVE-2021-30492?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.