Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› Cross-Site History Manipulation (XSHM)
Threats, Abuse & Incident Response

Cross-Site History Manipulation (XSHM)

← Back to Glossary
By NHI Mgmt Group Updated November 18, 2026 Domain: Threats, Abuse & Incident Response

Cross-Site History Manipulation is a browser attack that changes a user's navigation history by making cross-site requests or triggering redirects, so the back and forward buttons reveal or revisit attacker-chosen pages. It relies on normal browser history behaviour, not direct script access to another site's data, and can mislead navigation or state handling.

What XSHM Actually Exploits in the Browser

Cross-Site History Manipulation works because browsers preserve navigation history across ordinary page loads and redirects. The attack does not need to read another site’s contents; it only needs to influence which pages get entered into history, so later back and forward navigation can become a misleading control surface.

The practical security issue is trust in browser state. A user may believe the history stack reflects their own path, but an attacker can shape that path through cross-site requests, intermediate redirects, or state changes that make the browser revisit attacker-chosen locations.

How XSHM Misleads Users and Breaks State Assumptions

XSHM is dangerous because history is often treated as a neutral convenience feature rather than part of the application’s security model. If a workflow assumes the browser history only records deliberate user navigation, attacker-driven history entries can disrupt flow, confuse the user, or trigger page logic that was never intended to run in that sequence.

This matters most when applications use navigation position as an implicit signal of trust, progress, or continuity. A back-button action that lands on an unexpected page can lead to mistaken approvals, abandoned transactions, or a false belief that the user has safely returned to a known state.

Good browser-side design avoids assuming history is authoritative state. Sensitive actions should be bound to explicit server-side state and revalidated on each step, not inferred from where the user appears to be in the session.

Common Conditions That Make XSHM Possible

XSHM usually needs little more than normal browser behaviour and a page flow that can be influenced by cross-site navigation. Redirect chains, login and logout transitions, and application flows that depend on back-button behaviour are common places where the attack becomes visible.

Because the technique relies on history semantics rather than direct same-origin data access, it can bypass assumptions that only scriptable cross-site actions are dangerous. That is why browser history should be treated as a potentially attacker-influenced state channel, especially in workflows with sensitive transitions or recoverable actions.

Defensive Design for History-Safe Web Flows

Defending against XSHM is mostly about removing security dependence on the browser’s navigation record. Applications should tolerate unexpected back and forward navigation, avoid exposing sensitive intermediate pages, and ensure that critical actions are not completed or re-executed simply because a user revisits a prior view.

For broader cross-site navigation and leak hardening, practitioners can also anchor their controls in XS-Leaks Guide, which covers related browser-side leak families and the isolation headers that reduce cross-site exposure. Where navigation itself is part of the problem, the Fetch Metadata and Resource Isolation Policy Guide helps servers identify and reject cross-site requests before they can shape state. If the issue is broader web-app attack handling, the Web Application Attacks Guide places XSHM in the context of other request-driven abuse patterns.

Risk and Threat Considerations

XSHM creates a real integrity and usability risk because it lets an attacker manipulate how a victim moves through a site without needing to break same-origin protections. That can mislead users, distort auditability of the journey they actually took, and make navigation-dependent workflows behave as if the user chose actions they did not intend.

Failure mechanism: Cross-site requests and redirects populate the browser history with attacker-shaped entries, so later back and forward navigation revisits unexpected pages or replays a misleading path through the application.

Impact: Users may make trust decisions on the basis of a false navigation trail, sensitive flows may break or be resumed in the wrong state, and defensive assumptions about “where the user came from” can fail.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0, NIST SP 800-53 Rev 5, OWASP ASVS and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0PR.AA-05 — Identity and Access ManagementXSHM affects trusted user flow and state handling
Recommendation — Treat navigation-dependent flows as untrusted state and revalidate each sensitive step.
NIST SP 800-53 Rev 5SC-7 — Boundary ProtectionXSHM is shaped by cross-site request boundaries and redirect control
Recommendation — Restrict cross-site request paths and enforce strict boundary controls on sensitive flows.
OWASP ASVSV12 — Secure CommunicationXSHM mitigation depends on secure handling of cross-site navigation and request context
Recommendation — Enforce request-context checks and hardened browser-facing communication paths.
CIS Controls v8CIS-16 — Application Software SecurityXSHM is a web application behavior issue requiring secure design and testing
Recommendation — Test browser navigation flows for attacker-influenced state changes before release.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 18, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org