CVE-2024-22203
CWE-918Published: January 23, 2024· Updated: Jun 17, 2026
Official Description
Whoogle Search is a self-hosted metasearch engine. In versions prior to 0.8.4, the `element` method in `app/routes.py` does not validate the user-controlled `src_type` and `element_url` variables and passes them to the `send` method which sends a GET request on lines 339-343 in `request.py`, which leads to a server-side request forgery. This issue allows for crafting GET requests to internal and external resources on behalf of the server. For example, this issue would allow for accessing resources on the internal network that the server has access to, even though these resources may not be accessible on the internet. This issue is fixed in version 0.8.4.
Risk Analysis
Whoogle Search versions prior to 0.8.4 contain an SSRF vulnerability in the element method, allowing attackers to force the server to make unauthorized GET requests. This critical flaw is remotely exploitable and carries a CVSS score of 9.8. It poses a significant risk of internal network exposure.
No public exploit is known, and the vulnerability is not in CISA KEV. The flaw is remotely exploitable.
Upgrade to Whoogle Search version 0.8.4 or later. Ensure the application is configured to prevent unauthorized requests to internal network segments.
Technical Analysis
CVE-2024-22203 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.
The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.
A successful exploit results in complete confidentiality breach (data exposure), full integrity compromise (data manipulation), availability disruption (denial of service), with a CVSS base score of 9.8.
CVSS v3.1 Vector Breakdown
Affected Vendors & Products
Exploit & PoC Resources
Official Patches & Advisories
All References (14)
Quick Facts
Related CVEs (CWE-918)
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2024-22203 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts