---
id: "CVE-2026-116535"
kind: "vulnerability"
aliases: ["CVE-2026-116535"]
title: "SEOPress WordPress plugin: stored script injection through display names"
severity: "medium"
cvss: 6.4
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "self-hosted", "seopress", "wordpress"]
not_affected_if: ["no-public-registration", "plugin-not-installed", "version-above-10.3"]
published_at: "2026-10-31T08:16:48+00:00"
first_seen_at: "2026-10-31T08:34:28+00:00"
updated_at: "2026-10-31T08:35:09+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116535", "first_seen_at": "2026-10-31T08:34:28+00:00"}]
---

# SEOPress WordPress plugin: stored script injection through display names

The SEOPress WordPress plugin up to and including version 10.3 fails to escape a user's display name, so a subscriber can store a script that runs in pages other visitors open. An attacker gets script execution in the browser of whoever loads the injected page, including administrators.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed SEOPress version in the WordPress plugins screen or the plugin file header
- Look for `seopress` in the plugin directory listing on the server
- Check whether subscriber accounts can register on the site

## Fix

- Move to a SEOPress release newer than `10.3`; the exact fixed version is unknown from the sources

## Timeline

- 2026-10-31T08:34:28+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-116535

## From the sources

The SEOPress – AI SEO Plugin & On-site SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'display_name' parameter in all versions up to, and including, 10.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by any Subscriber who sets their display_name to a string containing the literal %%archive_title%% token alongside HTML event-handler payloads, as WordPress stores display names without HTML filtering and the plugin substitutes the token after escaping has already occurred.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_