GCVE - cpe:2.3:a:whoogle-search_project:whoogle-search:*:*:*:*:*:*:*:*

Approved changes feed: RSS · Atom

cpe:2.3:a:whoogle-search_project:whoogle-search:*:*:*:*:*:*:*:*

part: a version: * update: *

Vendor	Whoogle Search Project (`b9f0d168-4872-5a3e-9412-6624d8931656`)
Product	Whoogle Search (`78da31b9-d288-57f2-9963-1c50cf4d1d68`)
Edition	*
Language	*
Software edition	*
Target software	*
Target hardware	*
Other	*

Notes

Imported from purl2cpe mapping

PURL	Source	Last updated
`pkg:docker/benbusby/whoogle-search`	purl2cpe	2026-06-01 10:15:45.703111
`pkg:github/benbusby/whoogle-search`	purl2cpe	2026-06-01 10:15:45.703114
`pkg:github/trhacknon/whoogle-search`	purl2cpe	2026-06-01 10:15:45.703116
`pkg:pypi/whoogle-search`	purl2cpe	2026-06-01 10:15:45.703119

Identifier	cpeApplicability	Submitted	db.gcve.eu details	Rationale
`CVE:CVE-2022-25303`	vulnerable	2026-06-08 05:41:45.690228	Cross-site Scripting (XSS) MEDIUM (5.4) The package whoogle-search before 0.7.2 are vulnerable to Cross-site Scripting (XSS) via the query string parameter q. In the case where it does not contain the http string, it is used to build the error_message that is then rendered in the error.html template, using the [flask.render_template](https://flask.palletsprojects.com/en/2.1.x/api/flask.render_template) function. However, the error_message is rendered using the [\| safe filter](https://jinja.palletsprojects.com/en/3.1.x/templates/working-with-automatic-escaping), meaning the user input is not escaped. Published: 2022-07-12T14:20:11.761Z Updated: 2024-09-16T19:14:22.978Z Open on db.gcve.eu Reference links https://snyk.io/vuln/SNYK-PYTHON-WHOOGLESEARCH-2803306 https://github.com/benbusby/whoogle-search/blob/6d362ca5c7a00d2f691a2512461c5dfbfc01cbb3/app/routes.py%23L448 https://github.com/benbusby/whoogle-search/commit/abc30d7da3b5c67be7ce84d4699f327442d44606	Imported from gcve-enriched-dumps CVE data

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.