LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25266: An issue was discovered in Docmosis Tornado prior to version 2.9.5.

An issue was discovered in Docmosis Tornado prior to version 2.9.5. An authenticated attacker can change the Office directory setting pointing to an arbitrary remote network path. This triggers the execution of the soffice binary under the attackers control leading to arbitrary remote code execution (RCE).

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Docmosis Tornado before 2.9.5 lets an authenticated attacker change an Office directory setting so the application runs an attacker-controlled soffice binary. In business terms, a valid account could become full remote code execution on the server, risking data theft, service disruption, and wider compromise.

Executive priority

Prioritize remediation for any production or externally reachable Tornado instance. The issue requires authentication, but successful abuse can result in full server compromise. Upgrade and access-review work should be handled as a high-priority exposure reduction task.

Technical view

The CVE describes authenticated network RCE through a configurable Office directory path in Docmosis Tornado prior to 2.9.5. By pointing that setting at an arbitrary remote network path, the application may execute a malicious soffice binary. CVSS 3.1 is 8.8 with low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to organizations running Docmosis Tornado versions earlier than 2.9.5 where authenticated users can reach and alter the Office directory setting. Risk rises if the Tornado interface is broadly reachable or if low-privilege accounts can access configuration functions.

Exploitation context

The source bundle includes a public write-up and CVE details, but it does not show CISA KEV listing or confirmed active exploitation. Treat this as a serious authenticated RCE with public technical discussion, not as proven in-the-wild exploitation based on the provided evidence.

Researcher notes

The affected product metadata in the bundle is sparse, but the CVE description identifies Docmosis Tornado prior to 2.9.5. Avoid assuming broader Docmosis product impact. Focus validation on version, configuration access, and evidence of Office directory tampering.

Mitigation direction

  • Upgrade Docmosis Tornado to version 2.9.5 or later.
  • Check Docmosis release notes and guidance for any additional vendor-specific actions.
  • Restrict access to Tornado configuration functions to trusted administrators only.
  • Limit network reachability to the Tornado management surface where operationally possible.
  • Review the Office directory setting for unexpected remote or untrusted paths.

Validation and detection

  • Inventory all Docmosis Tornado deployments and record their exact versions.
  • Confirm no deployment is running a version earlier than 2.9.5.
  • Review current Office directory configuration for unauthorized or remote path values.
  • Check application and authentication logs for suspicious configuration changes.
  • Verify only intended administrative users can modify Office directory settings.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-25266 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-25266Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.