Summary
NixOS-based deployments of the Odoo ERP/CRM package from 21.11 to before 25.11 and 26.05 expose the Odoo database manager to the public internet without any effective authentication.
Any unauthenticated user who can reach the Odoo HTTP endpoint may download or delete entire databases and associated file stores, leading to full compromise of business data.
Affected context
This vulnerability occurs specifically in NixOS-packaged Odoo installations where:
- Odoo is deployed with NixOS configuration defaults for versions 21.11 up to (but not including) 25.11 and 26.05
- The
/web/databasedatabase manager endpoint is reachable from untrusted networks (e.g., the public internet or shared internal networks) - Odoo cannot persist its master password to its configuration file due to NixOS's immutable configuration model
Under these conditions, the database manager operates without reliable authentication, effectively exposing Odoo's databases and file store to anyone who can reach the service.
Exploit preconditions
- Attack surface: HTTP interface of the Odoo application, specifically the
/web/databasepath - Required access: Network-level connectivity to the Odoo instance (no prior authentication or credentials required)
- Trigger point: Visiting or programmatically interacting with the database manager endpoint to list, download, or delete databases
- Why exploitation is possible:
- The master password that normally protects the database manager cannot be persisted in Odoo's configuration on NixOS.
- After service restarts, Odoo behaves as if no master password is set and invites password setup via the public UI.
- This setup flow does not require existing authentication or administrative interaction, leaving the interface effectively unauthenticated.
Why this happens
The underlying issue is a failure to enforce authentication and authorization on a highly sensitive administrative interface, mapping primarily to CWE-306: Missing Authentication for Critical Function.
In standard Odoo deployments, the database manager is guarded by a master password that is persisted to configuration storage and acts as an additional security layer.
In the NixOS packaging model, Odoo is prevented from modifying its own configuration file, so:
- The auto-generated master password cannot be written and persisted.
- Manually configured master passwords set via the web UI are lost across restarts.
As a result, the database manager can run without effective protection and is exposed by default on NixOS deployments, making critical data management functionality world-accessible.
This also reflects CWE-552: Files or Directories Accessible to External Parties, as database content and file storage become accessible to any external actor with network access.
Potential impact
- Unauthorized download of entire Odoo databases, including potentially sensitive business, financial, and personal data
- Deletion of one or more databases, causing service outages and data loss
- Exfiltration of Odoo's file store, including attachments, documents, and uploaded files
- Facilitation of downstream attacks such as identity theft, fraud, or spear phishing due to exposed customer and employee records
- Regulatory and compliance violations if protected or personal data is compromised
- Loss of business continuity and trust due to the complete compromise of ERP/CRM data
General mitigation guidance
Effective mitigation focuses on enforcing strong authentication for administrative endpoints and limiting network exposure of sensitive management interfaces.
Common pattern-based strategies include:
- Network-level isolation:
- Restrict access to the
/web/databaseendpoint (or the entire Odoo instance) using firewalls, reverse proxies, or VPNs. - Place Odoo behind an application gateway that only exposes user-facing paths to the public internet.
- Explicit authentication enforcement:
- Ensure that database management and administrative interfaces require robust, independent authentication (e.g., master password, SSO for admins) that is not bypassed by configuration persistence issues.
- Favor configuration strategies where secrets and admin credentials are injected from secure external stores rather than written by the application.
- Secure configuration-by-default:
- Configure Odoo so that database management functions are disabled or bound to localhost by default in production contexts.
- Use NixOS or similar declarative configuration to explicitly set and persist the master password and other security-critical options outside of the application's runtime modification path.
- Least privilege and separation:
- Separate administrative tasks (database creation, backup, deletion) from normal user operations, using dedicated admin interfaces and restricted network paths.
- Minimize the number of operators with access to database management operations.
- Monitoring and operational hygiene:
- Centralize and monitor HTTP access logs for suspicious requests to
/web/databaseand similar endpoints. - Define operational runbooks for quickly decommissioning or reconfiguring exposed instances.
How teams detect issues like this
Detecting this class of vulnerability often involves both configuration analysis and runtime monitoring:
- Configuration and infrastructure review:
- Audit NixOS configuration for Odoo to verify how the master password is set and persisted.
- Check that the database manager endpoint is not exposed to untrusted networks (e.g., review firewall rules, reverse proxy configs, and service bindings).
- Static and policy-based checks:
- Use infrastructure-as-code scanning tools or custom policies to flag Odoo services where:
/web/databaseis reachable from the internet.- Admin interfaces are not protected by authentication guards or IP restrictions.
- Implement CI checks for Odoo-related NixOS modules to ensure secure defaults (e.g., disabling public database manager access).
- Log and traffic analysis:
- Analyze web server and Odoo logs for access to
/web/databaseand related routes, especially from unknown or suspicious IPs. - Use intrusion detection systems (IDS) or WAF rules to alert on patterns indicative of database listing or download requests.
- Automated security testing:
- Include authenticated and unauthenticated scans in application security testing to detect exposed administrative endpoints.
- Periodically run network scans against deployment environments to identify Odoo database manager exposure on externally reachable interfaces.

