CVE-2021-26722 json
LinkedIn Oncall vulnerable to Cross-Site Scripting
published 5y ago modified 4mo ago also GHSA-rfw2-x9f8-2f6m , PYSEC-2021-33 , EUVD-2021-0159
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
LinkedIn Oncall through 1.4.0 allows reflected XSS via /query because of mishandling of the "No results found for" message in the search bar.
Patch / fix
Is CVE-2021-26722 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.20% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/linkedin/oncall/issues/341 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | oncall | <1.4.1 |
1.4.1 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/linkedin/oncall/commit/843bc106a1c1b1699e9e52b6b0d01c7efe1d6225
web
-
github.com
/linkedin/oncall/issues/341
web, exploit, issue-tracking, third-party-advisory, report
-
nvd.nist.gov
/vuln/detail/CVE-2021-26722
advisory
-
github.com
/advisories/GHSA-rfw2-x9f8-2f6m
advisory
-
github.com
/linkedin/oncall
package
-
github.com
/pypa/advisory-database/tree/main/vulns/oncall/PYSEC-2021-33.yaml
web
-
pypi.org
/project/oncall
web
Sources
- CVE List CVE-2021-26722
- GitHub Advisory GHSA-rfw2-x9f8-2f6m
- NVD CVE-2021-26722
- OSV PYSEC-2021-33
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.