Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2020-35580: LFI in SearchBlox FileServlet (pre-9.2.2)

Published May 20, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS14.0%97th percentile
CISA KEVNoNot listed
In the wildReported272 exploitation records in Mallory
Vendor
Searchblox
IdentifiersCVE-2020-35580CWE-22 · Improper Limitation of a Pathname…

A local file inclusion (LFI) vulnerability exists in the FileServlet component of SearchBlox versions prior to 9.2.2. The vulnerability allows remote, unauthenticated attackers to read arbitrary files from the underlying operating system by sending crafted requests to /searchblox/servlet/FileServlet with manipulated parameters. Attackers can leverage this to access sensitive files, including the SearchBlox configuration file, which contains the Super Admin's API key and base64-encoded SHA1 password hashes of other users.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote, unauthenticated attackers to read arbitrary files on the server, including sensitive configuration files. This can lead to the exposure of the Super Admin's API key and password hashes for all users, potentially enabling further compromise of the application and underlying system.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict access to the /searchblox/servlet/FileServlet endpoint using network-level controls (e.g., firewall rules) or web server configuration. Monitor logs for suspicious requests to this endpoint and consider disabling the vulnerable servlet if not required.

Remediation

Patch, then assume compromise.

Upgrade SearchBlox to version 9.2.2 or later, where this vulnerability has been addressed. Ensure that all instances are patched promptly to prevent exploitation.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SearchbloxSearchbloxapplication
FAQ

Frequently asked questions

Is CVE-2020-35580 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-35580?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2020-35580.
Is there a patch for CVE-2020-35580?
Upgrade SearchBlox to version 9.2.2 or later, where this vulnerability has been addressed. Ensure that all instances are patched promptly to prevent exploitation.
What products are affected by CVE-2020-35580?
Searchblox.
How severe is CVE-2020-35580?
CVE-2020-35580 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 14.0% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.