CVE-2021-43561 — google-for-jobs
MEDIUMCVE-2021-43561 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in pegasus/google-for-jobs. A fix is available for pegasus/google-for-jobs — see the affected versions and patch details below.
Cross-site Scripting in pegasus/google-for-jobs
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-43561 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
pegasus/google-for-jobs🐘pegasus/google-for-jobsReal-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
An XSS issue was discovered in the google_for_jobs (aka Google for Jobs) extension before 1.5.1 and 2.x before 2.1.1 for TYPO3. The extension fails to properly encode user input for output in HTML context. A TYPO3 backend user account is required to exploit the vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | pegasus/google-for-jobs | all versions | 1.5.1composer require pegasus/google-for-jobs:^1.5.1 |
| 🐘Packagist | pegasus/google-for-jobs | ≥ 2.0.0&&< 2.1.1 | 2.1.1composer require pegasus/google-for-jobs:^2.1.1 |
Affected Products
google for jobspega-susDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pegasus/google-for-jobs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pegasus/google-for-jobs to 1.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-43561 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
Is CVE-2021-43561 in your dependencies?
Find it across Packagist, including transitive dependencies.