S4E just found a high top 10 tcp port service scan
critical·Misconfiguration·Updated Jul 1, 2026

CVE-2026-56782 Scanner

CVE-2026-56782 Scanner - Unauthenticated Access vulnerability in Gorse

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
0
Times Used
by S4E users
0
Assets Scanned
domains & IPs
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2026-56782
9.3
CVSScritical
Exploitable remotely over the internet · no authentication required.

Gorse before 0.5.10 contains an authentication bypass vulnerability in the /api/dump and /api/restore endpoints that allows unauthenticated attackers to access protected functionality when admin_api_key is empty, which is the default configuration. Remote attackers can exfiltrate the entire database including user records, items, and feedback data containing personally identifiable information, or completely overwrite the dataset without authentication.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
gorseby gorse-io
AFFECTED< 0.5.10SAFE ✓≥ 0.5.10
Updated Aug 5, 2026View on NVD →
Detail

Gorse is an open-source recommendation system utilized primarily by companies and developers to power personalized content recommendations on websites, applications, and other digital platforms. It is popular for its efficiency and scalability, providing businesses with the ability to handle a large number of users and products. Companies leverage Gorse's capabilities to improve user engagement, drive conversions, and enhance the overall customer experience. The software is generally used by data scientists, software developers, and analysts who seek to optimize recommendation algorithms and deliver highly targeted content. Its deployment often spans various sectors, including e-commerce, media, and entertainment, where personalized recommendations are critical. With its customizable features, Gorse enables users to tailor recommendations according to specific business needs or user behavior analysis.

The vulnerability identified in Gorse versions prior to 0.5.10 pertains to unauthenticated access, where the system lacks enforcement of proper authentication checks. This flaw permits remote attackers to bypass authentication mechanisms due to the presence of an empty admin_api_key setting. By exploiting this weakness, attackers can gain unauthorized access to sensitive functions, specifically at the /api/dump and /api/restore endpoints of the application. As a result, the integrity and confidentiality of the application's data can be severely compromised. This type of vulnerability is critical as it exposes sensitive user information to potential exploitation by malicious actors. Administrators must recognize the severity of this flaw and prioritize remediation efforts to safeguard their data and application infrastructure.

Technical details reveal that the vulnerability exists primarily due to the system's reliance on a default, empty admin_api_key, which attackers can easily manipulate. The impacted endpoints, /api/dump and /api/restore, are designed for database operations but are improperly protected under this configuration. Attackers can craft requests that leverage the unauthenticated endpoints to either exfiltrate or alter comprehensive database contents. Evidence of this vulnerability's exploitability is demonstrated when unauthorized transactions succeed without a valid admin_api_key, as the system does not generate error messages for authorization failures. These conditions underscore the necessity for immediate configuration reviews and security enhancement in affected Gorse deployments.

The exploitation of this vulnerability by unauthorized individuals could result in significant adverse effects on the organization employing Gorse. Critical user data could be exposed or, worse, manipulated, leading to potential data breaches and loss of consumer trust. An unauthorized database dump might disclose confidential information, including personally identifiable information (PII) or financial details. Additionally, attackers could corrupt data or introduce malicious content, disrupting normal operations. Persistent exploitation could cause long-term reputational damage and potential legal ramifications due to the exposure of sensitive information under data protection regulations.

REFERENCES

Solution Advice
  • Update Gorse to version 0.5.10 or later to ensure authentication mechanisms are effective.
  • Review and configure the admin_api_key setting to avoid default and empty values, ensuring robust access control practices.
  • Implement additional security measures such as token authentication to further protect sensitive endpoints.
  • Conduct regular security audits to identify and rectify potentially vulnerable configurations.
  • Educate the IT team on secure deployment practices to prevent similar issues in the future.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.