CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-55779

CVE-2026-55779: Stored Cross-Site Scripting (XSS) in Silverstripe Archive Admin Restore

Amit Schendel
Amit Schendel
Senior Security Researcher

Aug 29, 2026·6 min read·26 visits

Executive Summary (TL;DR)

Unescaped user input in the RestoreAction helper leads to stored XSS inside the Silverstripe CMS administrative interface during page restoration actions.

A Stored Cross-Site Scripting (XSS) vulnerability exists in the silverstripe/versioned package prior to version 3.2.1. When an administrator restores an archived page containing a crafted Title or URLSegment, the generated restoration message is rendered as CAST_HTML without proper sanitization. This allows malicious JavaScript to execute in the administrator's browser session, compromising the confidentiality and integrity of the CMS dashboard.

Vulnerability Overview

The affected component is the RestoreAction helper within the silverstripe/versioned module, which manages the lifecycle, tracking, and restoration of versioned models in Silverstripe CMS applications. When an administrator accesses the ArchiveAdmin console and restores a previously archived object, the module constructs an execution status message. This message incorporates the restored object's metadata, such as its Title, URLSegment, and CMSEditLink.

Because the system treats system messages as validated HTML under the CAST_HTML formatting configuration, it does not perform automatic output sanitization on the rendered output. This behavior exposes a stored cross-site scripting (XSS) attack surface. Specifically, any malicious input stored in the draft or published attributes of a versioned page will bypass standard framework output filters and execute in the target's browser.

The vulnerability is tracked under CVE-2026-55779. It represents a classic improper neutralization of input during web page generation (CWE-79). The security impact is determined by the permissions of the user restoring the content. Since page restoration is restricted to administrative roles, the vulnerability targets high-privilege sessions within the CMS control panel.

Root Cause Analysis

The root cause of CVE-2026-55779 is the lack of output encoding within the getRestoreMessage method located in src/RestoreAction.php. The Silverstripe framework relies on casting rules to distinguish between plain text and rich HTML. When generating notification payloads, the framework treats the output as trusted HTML, assigning it a casting type equivalent to CAST_HTML.

In the vulnerable implementation, the getRestoreMessage method directly interpolates the title of the restored object ($restoredItem->Title) and its corresponding CMS edit URL into the notification string. This interpolation is executed via sprintf and string concatenation. Because these values originate from user-controlled fields and are stored within the database without restrictive input filtering, they serve as persistent vectors for injection payloads.

When the database stores malicious markup and subsequently retrieves it for display in the ArchiveAdmin, the lack of sanitization allows the markup to be rendered directly into the administrative UI. This bypasses the browser's same-origin boundary protections, allowing the executed script to make requests on behalf of the authenticated administrator.

Code Analysis

The vulnerable logic resides in src/RestoreAction.php inside the getRestoreMessage function. In unpatched releases, the raw property values were assigned and used without any defensive filtering.

// Vulnerable Code Path
public static function getRestoreMessage($originalItem, $restoredItem, $changedLocation = false)
{
    // Raw Title is assigned directly without escaping
    $restoredID = $restoredItem->Title ?: $restoredItem->ID;
    $restoredType = Convert::raw2xml(strtolower($restoredItem->i18n_singular_name() ?? ''));
 
    $editLink = $restoredItem->CMSEditLink();
    if ($editLink) {
        // Unescaped restoredID and editLink are concatenated into an HTML anchor tag
        $restoredID = sprintf('<a href="%s">%s</a>', $editLink, $restoredID);
    }
    // ...
}

The fixing patch introduces Convert::raw2xml calls to properly escape all dynamic parameters. This utility is the standard Silverstripe mechanism for converting unsafe characters into XML entities.

// Patched Code Path
public static function getRestoreMessage($originalItem, $restoredItem, $changedLocation = false)
{
    // Escape the Title or ID property to prevent tag injection
    $restoredID = Convert::raw2xml($restoredItem->Title ?: $restoredItem->ID);
    $restoredType = Convert::raw2xml(strtolower($restoredItem->i18n_singular_name() ?? ''));
 
    $editLink = $restoredItem->CMSEditLink();
    if ($editLink) {
        // Escape both the target URL and the inner anchor text
        $restoredID = sprintf('<a href="%s">%s</a>', Convert::raw2xml($editLink), $restoredID);
    }
    // ...
}

Additionally, the patch applies Convert::raw2xml to the values generated during difference analysis. When the original Title or URLSegment differs from the restored state, the system records the new values. These must be escaped because they are subsequently rendered to describe the property modifications.

Exploitation

An attacker can exploit this vulnerability using multiple vectors depending on the configured fields. The primary vector involves the Title attribute of a page. The attacker injects an iframe payload containing a nested script tag: <iframe srcdoc="&lt;script&gt;alert('xss')&lt;/script&gt;"></iframe>. Once this page is archived, the payload resides in the historical versions tables.

The second vector exploits the change-tracking output when a page property is altered. By crafting a payload using the formaction attribute on a button, such as <button formaction="javascript:alert(1)">Click</button>, the attacker targets the administrator's UI interaction. If the restored page's Name differs from the original, this dynamic block is evaluated and rendered in the success message.

Both attack vectors require the victim to perform a page restoration action. While this introduces a dependency on user interaction, administrative actions of this type are routine during content maintenance cycles, making social engineering or passive waiting highly viable strategies.

Impact Assessment

The security impact of CVE-2026-55779 is rated as Medium, with a CVSS v3.1 base score of 5.4. Although the impact is localized to the client session, the administrative nature of the targeted workspace elevates the operational consequences. The injected script executes under the origin and session credentials of the active administrator.

The attacker can read, modify, or exfiltrate sensitive data, including CSRF tokens, session identifiers, and CMS settings. Because Silverstripe administrators have full write access to the underlying application database via the site tree and settings panels, the session context can be used to perform authorized actions. This includes the creation of backdoored administrator accounts, modifying site configurations, or injecting malicious scripts into public pages.

While the scope is classified as Unchanged because the execution is confined to the client browser, the administrative privileges of the compromised user effectively grant the attacker complete logical control over the CMS content. No active exploitation has been registered in the wild, but the existence of explicit regression tests in the codebase demonstrates a straightforward exploitation path.

Remediation & Mitigation

The primary remediation for this vulnerability is upgrading the silverstripe/versioned package to version 3.2.1 or newer. This update ensures that all parameters processed by RestoreAction::getRestoreMessage are securely escaped prior to HTML assembly.

composer update silverstripe/versioned

If immediate package upgrade is not feasible, organizations can manually apply the hotfix by modifying src/RestoreAction.php. The modification requires wrapping all dynamic user-controlled strings, including $restoredItem->Title, $restoredItem->URLSegment, and $editLink, inside calls to the Convert::raw2xml helper.

To detect potential exploitation attempts or pre-existing payloads, security teams should execute database queries across historical version tables. The query targets instances of common HTML tags and attributes inside the Title and URLSegment columns:

SELECT ID, Title, URLSegment FROM "SiteTree_Versions" 
WHERE Title LIKE '%<script%' OR Title LIKE '%<iframe%' OR Title LIKE '%formaction%';

Fix Analysis (2)

Technical Appendix

CVSS Score
5.4/ 10
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Affected Systems

Silverstripe CMSSilverstripe Versioned Module

Affected Versions Detail

Product
Affected Versions
Fixed Version
silverstripe/versioned
Silverstripe
< 3.2.13.2.1
AttributeDetail
CWE IDCWE-79
Attack VectorNetwork (AV:N)
CVSS Score5.4 (Medium)
EPSS ScoreNot Available
ImpactStored Cross-Site Scripting / Session Hijacking
Exploit StatusPoC Available
KEV StatusNot Listed

MITRE ATT&CK Mapping

T1189Drive-by Compromise
Initial Access
T1185Browser Session Hijacking
Collection
CWE-79
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

The application fails to neutralize or escape user-controlled inputs before placing them into dynamic HTML messages rendering to administrators.

Known Exploits & Detection

GitHub AdvisoryStored XSS PoC details via title-based and button-based vectors

Vulnerability Timeline

Security patch authored
2026-06-15
Pull request #541 merged
2026-06-24
Vulnerability published and patch released in version 3.2.1
2026-08-28

References & Sources

  • [1]GitHub Security Advisory
  • [2]Pull Request #541
  • [3]Fix Commit
  • [4]Test Commit
  • [5]Release 3.2.1
  • [6]Silverstripe Security Release

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•20 minutes ago•GHSA-7MR3-28H5-M5VX
7.7

GHSA-7mr3-28h5-m5vx: Authorization Bypass and Cross-Project Volume Copy in Canonical LXD

An authorization bypass vulnerability in Canonical LXD (tracked as GHSA-7mr3-28h5-m5vx and CVE-2026-55621, and as GHSA-64f3-v33m-w89f in Linux Containers Incus) allows an authenticated user with restricted project access to copy custom storage volumes and volume snapshots from unauthorized projects. The flaw resides in the storagePoolVolumesPost REST API handler, which verifies permissions on the destination project but fails to check whether the caller holds view entitlements on the source project or volume specified in the request body.

Alon Barad
Alon Barad
1 views•10 min read
•about 1 hour ago•GHSA-47W9-6R3F-938G
9.9

GHSA-47w9-6r3f-938g: Authorization Bypass and Host Root Command Execution in Canonical LXD and Incus

A missing authorization and configuration validation vulnerability in Canonical LXD and LXC Incus allows authenticated users within restricted projects to bypass project security boundaries. By smuggling prohibited low-level configuration directives (such as raw.lxc or raw.qemu) inside instance snapshots or backup archives, an attacker can restore these configurations within a restricted project and execute arbitrary commands with root privileges on the underlying host operating system.

Alon Barad
Alon Barad
3 views•11 min read
•about 2 hours ago•GHSA-JPF8-86F3-WP38
9.9

CVE-2026-48752: Arbitrary Host File Read and Write via Templates Symlink in Canonical LXD and Incus

A symbolic link traversal vulnerability (CWE-59) in Canonical LXD and Linux Containers Incus allows an authenticated user with image import permissions to read and write arbitrary files on the host filesystem. During image archive unpacking, the daemon fails to reject top-level symbolic links for the instance `templates` directory. Subsequent requests to the instance template API endpoints follow this symbolic link outside the instance storage directory with root privileges, enabling complete host compromise.

Amit Schendel
Amit Schendel
4 views•10 min read
•1 day ago•CVE-2026-12411
8.4

CVE-2026-12411: Cross-Guest Volume Hijack via DevLXD Device PATCH in Canonical LXD

CVE-2026-12411 is a broken access control vulnerability in the DevLXD interface of Canonical LXD versions 6.6 through 6.8. The flaw resides in the devLXDInstancePatchHandler component, which fails to verify storage volume ownership when an instance attaches a new disk device via the /dev/lxd guest socket. When the security.devlxd.management.volumes configuration option is enabled, an untrusted guest or DevLXD identity can issue a crafted HTTP PATCH request referencing another tenant's custom storage volume. The LXD host daemon subsequently mounts the target volume into the requesting guest, permitting unauthorized cross-tenant read and write operations.

Amit Schendel
Amit Schendel
7 views•10 min read
•1 day ago•CVE-2026-105769
9.3

CVE-2026-105769: Azure Entra ID Token Exfiltration in Kaniko via Unanchored ACR Hostname Regex

CVE-2026-105769 (GHSA-5q7h-w9jf-cx97, GO-2026-6225) is an origin validation error and credential exfiltration vulnerability affecting Kaniko prior to version 1.25.20. The flaw stems from an unanchored regular expression in the integrated Azure Container Registry (ACR) credential helper (github.com/chrismellard/docker-credential-acr-env). When Kaniko processes a Dockerfile containing an image reference hosted on a lookalike domain containing an ACR suffix as a substring (e.g., x.azurecr.io.attacker.com), the credential helper acquires a Microsoft Entra ID access token for Azure Resource Manager and transmits it via HTTP POST to the attacker-controlled host.

Amit Schendel
Amit Schendel
11 views•11 min read
•1 day ago•CVE-2026-62300
6.5

CVE-2026-62300: Uncontrolled Resource Consumption in filecoin-pin Daemon

CVE-2026-62300 is an uncontrolled resource consumption vulnerability (CWE-400) affecting the daemon mode of filecoin-pin in versions up to and including 1.1.0. The daemon implements the IPFS Pinning Service API to store content on Filecoin's Proof of Data Possession (PDP) service. Due to the absence of rate limits, concurrency caps, execution timeouts, and Directed Acyclic Graph (DAG) traversal limits, an authenticated user—or an unauthenticated user when authentication is disabled—can exhaust system resources via crafted POST /pins requests.

Amit Schendel
Amit Schendel
9 views•11 min read