/

CVE-2026-78834

Severity:

HIGH RISK

(8.8)

Code Injection (CWE-94) in CMSimple CoAuthors Plugin Feature

CVE-2026-78834

Deferred

Vulnerability type

Category:

Code Injection

CWE:

CWE-94

Impact:

Server-Side Code Execution

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

CMSimple 5.22 contains a code execution vulnerability in the CoAuthors plugin's content import feature. An authenticated low-privileged user who can modify page content and control imported text may cause server-side code execution when crafted external or uploaded content is referenced.

Affected context

The vulnerability occurs in CMSimple deployments using the CoAuthors plugin and its affected content import functionality. Risk is present where a low-privileged authenticated user can modify page content and influence the external or uploaded text content referenced by an import operation.

Exploit preconditions

  • Attack surface: The CoAuthors plugin's content import feature
  • Required access: An authenticated account with permission to modify page content
  • Trigger point: Processing imported external or uploaded text content referenced by page content
  • Why exploitation is possible: Attacker-controlled content is processed in a server-side execution context without adequately preventing code-like interpretation

Why this happens

The underlying issue is an unsafe boundary between user-controlled imported content and server-side code processing. The affected functionality permits crafted content references to reach an execution-capable processing path rather than treating the imported material strictly as inert data. This behavior maps to CWE-94: Improper Control of Generation of Code, because attacker-influenced input can affect code interpretation or execution.

Potential impact

  • An attacker may execute arbitrary code with the privileges of the CMS process.
  • The attacker could access, modify, or delete application data.
  • The vulnerability can enable website defacement or content manipulation.
  • A compromised CMS process may be used to access adjacent services or stored secrets.
  • The incident could affect the confidentiality, integrity, and availability of the hosting environment.

General mitigation guidance

Mitigation generally focuses on ensuring imported content remains data rather than executable logic.

Common defensive patterns include:

  • Restricting import functionality to trusted administrators or disabling unnecessary import paths
  • Treating external and uploaded content as untrusted regardless of the submitting user's authentication status
  • Using allowlisted content formats and non-executable parsing paths
  • Separating content rendering from server-side code evaluation
  • Applying strict authorization checks to page editing and import operations
  • Running the CMS with least-privilege service permissions and limiting access to sensitive files and services
  • Validating and isolating imported content before it reaches rendering or processing components

How teams detect issues like this

Organizations can look for this vulnerability class through:

  • Static analysis rules identifying dynamic evaluation, template execution, or code-generation paths fed by imported content
  • Code review checks for import handlers that combine user-controlled references with server-side interpreters
  • Tests covering uploaded and externally sourced content under low-privilege accounts
  • Web and application logs showing unusual import requests, unexpected external references, or content changes by non-administrative users
  • Policy enforcement that limits who may use content import features and restricts outbound content retrieval
  • Neutral automated security review tools that flag code execution sinks connected to user-controlled input

Sources

SourceLink
gist.github.comgist.github.com/AEQ3/574cb644306776a9ff1a0de30b085e62
github.comgithub.com/AEQ3/CVE/issues/1

Frequently asked

questions

Exploitation generally requires an authenticated account with permission to modify page content and influence imported text references. The required privileges may be available to users who are not full administrators.

It may be remotely triggered through normal CMS functionality when the affected import feature is exposed and the attacker has the required authenticated access.

Treat imported external and uploaded content as untrusted data, prevent it from reaching code-execution paths, and restrict the import feature to narrowly authorized users.

Use allowlisted, non-executable content formats; separate parsing from execution; apply least privilege; and test import features with low-privilege accounts and adversarial content.

Find out what's already
exploitable in your codebase.