EchoHS GeekezBrowser Public API status information disclosure
Affects GeekEZ Browser 1.7.1 with the Public API enabled. The sources list no vendor rating or fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects GeekEZ Browser 1.7.1 (CVE description covers up to 1.7.2/1.8.0). Public API must be enabled.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
EchoHS GeekezBrowser versions up to 1.8.0 contain a flaw in the Public API status endpoint that can leak sensitive information to a local user. The exploit details are public, so the issue should be addressed by upgrading the affected software.
Read the original description
A vulnerability was detected in EchoHS GeekezBrowser up to 1.7.2/1.8.0. This affects an unknown part of the file /api/status of the component Public API. The manipulation results in information disclosure. The attack requires a local approach. The exploit is now public and may be used. Upgrading to version 1.8.1 is able to mitigate this issue. The patch is identified as 9317a89aa0fd2715d9c2bd27bdbb52b5d228dd9e. Upgrading the affected component is recommended.
What to do
Check whether your setup matches what the bug needs.
Affects GeekEZ Browser 1.7.1 (CVE description covers up to 1.7.2/1.8.0). Public API must be enabled.Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- EchoHS GeekezBrowser
1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.7.0, 1.7.1, 1.7.2, 1.8.0
Evidence 8
- Advisory
- Advisory
- Advisory
- Advisory
- Patch
Show all 8 sourcesShow fewer sources
- Patch
- Exploit
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120503
What does this mean?
A web page can read the browser's local anti-detect state, which lets it identify a GeekEZ user and see their fingerprint-management settings. When the Public API is enabled, profiles can also be created or changed without authentication.Source: github.com
Am I affected, and how do I check?
The checked facts name GeekEZ Browser 1.7.1, and the CVE description covers up to 1.7.2 and 1.8.0. The bug only matters when the Public API is enabled, so check the browser's version and whether that API setting is on.Source: github.com
What should I do about it?
The checked facts name no fixed version, so no upgrade target can be given. Keep the Public API disabled and watch the vendor's advisory for a fix.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data