dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-29597

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
DDSN Interactive cm3 Acora CMS version 10.7.1 contains an improper access control vulnerability. An editor-privileged user can access sensitive configuration files by force browsing the “/Admin/file_manager/file_details.asp” endpoint and manipulating the “file” parameter. By referencing specific files (e.g., cm3.xml), the attacker can retrieve system administrator credentials, SMTP settings, database credentials, and other confidential information. The exposure of this information can lead to full administrative access to the CMS, unauthorized access to email services, compromise of backend databases, lateral movement within the network, and long-term persistence by an attacker. This access control bypass poses a critical risk of account takeover, privilege escalation, and systemic compromise of the affected application and its associated infrastructure.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DDSN Interactive cm3 Acora CMS v10.7.1 has an improper access control vulnerability in the file_manager component. An attacker with editor-level privileges can force browse to /Admin/file_manager/file_details.asp and manipulate the 'file' parameter to access sensitive configuration files like cm3.xml, exposing admin credentials, SMTP settings, and database connection strings.

MitigationImplement proper authorization checks to ensure users can only access files within their assigned permissions scope. Validate file paths to prevent directory traversal and restrict access to sensitive configuration files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Acora CMS installation and version
    Inspect the application banner, check the main page footer, or look for version files in the web root directory. Compare the discovered version to v10.7.1.
    Affected if Acora CMS v10.7.1 is installed and running.
  2. Verify file_manager component is present
    Check for the existence of the /Admin/file_manager/ directory and specifically locate file_details.asp within the web application structure.
    Affected if The file_manager component with file_details.asp exists in the application.
  3. Confirm editor-level user accounts exist
    Review user role configurations or attempt to identify accounts with editor privileges through the application's user management interface or database.
    Affected if Editor-level user accounts are configured in the system.
  4. Test path traversal in file parameter
    With an editor-level account, attempt an authenticated request to /Admin/file_manager/file_details.asp?file=../../cm3.xml or similar path traversal sequences to access configuration files outside the intended directory.
    Affected if The application allows access to files outside the intended scope by manipulating the file parameter, exposing sensitive configuration files like cm3.xml.

A user is affected if running Acora CMS v10.7.1 with the file_manager component accessible to editor-level accounts, and the application permits directory traversal via the file parameter to access sensitive configuration files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks to ensure users can only access files within their assigned permissions scope. Validate file paths to prevent directory traversal and restrict access to sensitive configuration files.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29597 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29597 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data