Summary
Admidio's Docker image configuration causes Apache to ignore the .htaccess file that should protect uploaded documents, leaving them directly accessible over HTTP.
Any user who can learn or guess the file path, which is returned in the upload response JSON, may access uploaded files without authentication or regard for the configured role-based permissions.
Affected context
This vulnerability occurs in Admidio instances deployed via the affected Docker image, where Apache is configured with AllowOverride None.
In this context, the application relies on adm_my_files/.htaccess to enforce access controls on uploaded documents, but Apache silently ignores these rules.
As a result, documents uploaded via the documents module are stored under web-accessible paths that lack the intended HTTP-layer protection, regardless of the role-based permissions set in the UI.
Exploit preconditions
- Attack surface: HTTP access to the Admidio web server hosting the vulnerable Docker image.
- Required access: Ability to reach the web server over the network; no valid application account is required once a document path is known.
- Trigger point: Requesting the direct URL of an uploaded document under the documents module.
- Why exploitation is possible:
- Apache is configured with
AllowOverride None, so.htaccessrules inadm_my_files/are ignored. - Admidio's upload process returns the file path in JSON responses, disclosing the location of uploaded documents.
- The server does not perform an authorization check when files are accessed directly via their URL.
Why this happens
The core issue is an improper access control pattern where application-level authorization relies on a web server configuration that is not actually enforced.
Admidio expects .htaccess in adm_my_files/ to deny direct HTTP access to uploaded documents, but the Docker image configures Apache with AllowOverride None, effectively disabling these protections.
This mismatch between the assumed security model (per-directory access control) and the actual deployment configuration leads to a situation where sensitive files are publicly reachable without authentication, aligning with CWE-284: Improper Access Control.
Potential impact
- Exposure of documents that were intended to be restricted to specific roles or authenticated users.
- Leakage of personal, organizational, or confidential information contained in uploaded files.
- Facilitation of information-gathering for further attacks (e.g., discovering system details or internal processes described in documents).
- Potential compliance and privacy violations if regulated data is stored in the documents module.
General mitigation guidance
Mitigation centers on aligning the deployment configuration with the application's access-control assumptions and reducing reliance on .htaccess for security.
Recommended defensive patterns include:
- Ensuring web server configurations explicitly enforce directory-level access controls instead of relying on
.htaccesswhereAllowOverrideis disabled. - Placing uploaded files outside the web root and serving them through application endpoints that perform explicit authentication and authorization checks.
- Implementing defense-in-depth by checking permissions at the application layer on any file download, regardless of web server configuration.
- Minimizing the exposure of internal file paths in API responses, sharing only identifiers or opaque tokens that are validated server-side.
- Using least-privilege for document access paths and restricting directory listings to prevent enumeration of uploaded files.
How teams detect issues like this
High-level detection approaches for this class of misconfiguration and access control issues include:
- Configuration review: Systematically checking web server configurations (e.g., Apache's
AllowOverridesettings) to ensure they match application security assumptions. - Dynamic testing: Using automated or manual tools to crawl for accessible files under upload directories and verifying whether authorization is enforced on direct file URLs.
- Static analysis / code review: Identifying code paths that rely on
.htaccessor other server-level mechanisms instead of explicit application-layer checks for sensitive resources. - Logging and monitoring: Monitoring access logs for requests to upload directories and detecting anomalous access patterns (e.g., unauthenticated IPs fetching many document URLs).

