SEOPress vulnerability history: display names, tracking parameters and roles
An author display name, a profile field, analytics parameters and a social image URL all appear in SEOPress record titles.
Here is how to read those records, and where SEOPress keeps its tracking, template and role settings.
On this page
SEOPress vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 20 records for SEOPress. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 10.4
Worked out from data retrieved on .
Every affected range listed in this source for SEOPress ends before version 10.4.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
SEOPress <= 10.3 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'seopress_google_analytics_affiliate_tracking' and 'seopress_google_analytics_download_tracking' Parameters
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-120515
Affected versions- All versions up to and including 10.3
Patched versions: 10.4
Update to at least version 10.4.
SEOPress - AI SEO Plugin & On-site SEO < 10.4 - Authenticated (Custom Role+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-108041
Affected versions- All versions before 10.4
Patched versions: 10.4
Update to at least version 10.4.
SEOPress <= 10.3 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'display_name' Profile Field via %%archive_title%% Template Tag
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-116535
Affected versions- All versions up to and including 10.3
Patched versions: 10.4
Update to at least version 10.4.
SEOPress <= 10.2 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'seopress_google_analytics_matomo_id' Parameter
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.9)
- CVE:
- CVE-2026-101357
Affected versions- All versions up to and including 10.2
Patched versions: 10.3
Update to at least version 10.3.
SEOPress <= 10.2 - Unauthenticated Stored Cross-Site Scripting via Author Display Name
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2026-96564
Affected versions- All versions up to and including 10.2
Patched versions: 10.3
Update to at least version 10.3.
Show 15 older recordsHide the older records
SEOPress - AI SEO Plugin & On-site SEO <= 10.1 - Authenticated (Contributor+) Server-Side Request Forgery
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-85305
Affected versions- All versions up to and including 10.1
Patched versions: 10.2
Update to at least version 10.2.
SEOPress <= 8.1.1 - Missing Authorization
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2024-50455
Affected versions- All versions up to and including 8.1.1
Patched versions: 8.2
Update to at least version 8.2.
SEOPress <= 8.1.1 - Missing Authorization
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2024-50454
Affected versions- All versions up to and including 8.1.1
Patched versions: 8.2
Update to at least version 8.2.
SEOPress <= 8.1.1 - Missing Authorization
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2024-50456
Affected versions- All versions up to and including 8.1.1
Patched versions: 8.2
Update to at least version 8.2.
SEOPress - On-site SEO <= 8.1.1 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2024-9225
Affected versions- All versions up to and including 8.1.1
Patched versions: 8.2
Update to at least version 8.2.
SEOPress - On-site SEO <= 7.9 - Authenticated(Contributor+) Stored Cross-Site Scripting via Social Image URL
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2024-1168
Affected versions- All versions up to and including 7.9
Patched versions: 7.9.1
Update to at least version 7.9.1.
SEOPress <= 7.8 - Unauthenticated PHP Object Injection
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.0)
- CVE:
- CVE-2024-5488
Affected versions- All versions up to and including 7.8
Patched versions: 7.9
Update to at least version 7.9.
SEOPress <= 7.7.2 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2024-4899
Affected versions- All versions up to and including 7.7.2
Patched versions: 7.8
Update to at least version 7.8.
SEOPress <= 7.7.2 - Authenticated (Contributor+) Open Redirect
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2024-4900
Affected versions- All versions up to and including 7.7.2
Patched versions: 7.8
Update to at least version 7.8.
SEOPress - On-site SEO <= 7.5.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2024-1134
Affected versions- All versions up to and including 7.5.2.1
Patched versions: 7.6
Update to at least version 7.6.
SEOPress <= 7.6.1 - Information Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2024-34383
Affected versions- All versions up to and including 7.6.1
Patched versions: 7.7
Update to at least version 7.7.
SEOPress - On-site SEO <= 7.5.2.1 - Authenticated (Author+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2024-2165
Affected versions- All versions up to and including 7.5.2.1
Patched versions: 7.6
Update to at least version 7.6.
SEOPress - On-site SEO <= 7.2 - Authenticated (Admin+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.4)
- CVE:
- CVE-2023-6290
Affected versions- All versions up to and including 7.2
Patched versions: 7.3
Update to at least version 7.3.
SEOPress <= 6.5.0.2 - Authenticated (Administrator+) PHP Object Injection
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.6)
- CVE:
- CVE-2023-1669
Affected versions- All versions up to and including 6.5.0.2
Patched versions: 6.5.0.3
Update to at least version 6.5.0.3.
SEOPress 5.0.0 - 5.0.3 - Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2021-34641
Affected versions- Version 5.0.0 only
- Version 5.0.1 only
- Version 5.0.2 only
- Version 5.0.3 only
Patched versions: 5.0.4
Update to at least version 5.0.4.
Check SEOPress on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
Where SEOPress takes input, and who can reach it
SEOPress is a WordPress SEO plugin.
Its WordPress.org listing describes a universal SEO metabox for editing titles, descriptions, Open Graph, X Cards, schema, robots and canonical, plus XML and HTML sitemaps, Google Analytics 4 and Matomo tracking, and redirections at the post, page and custom post type level. Read a SEOPress vulnerability record against those places first.
The vendor's REST guide says the routes that write a post's SEO fields require the edit_post capability, and that a role checked in SEO > Advanced settings > Security cannot use them. It also says any user who can edit a post can enable its redirection, and that since SEOPress 10.4 the target must be on the site unless the user has the manage_options or unfiltered_html capability.
WordPress documents that a Contributor can write and manage its own posts but cannot publish them.
For settings pages, the vendor's capabilities guide says an administrator checks the roles allowed on each page under SEO, Advanced, Security.
SEOPress vulnerabilities on record: the values their titles name
Titles in the history on this page keep returning to Stored Cross-Site Scripting, and some name a value: an author display name, a profile field with a template tag, analytics parameters, a social image URL.
Others include Missing Authorization, PHP Object Injection, Server-Side Request Forgery, Open Redirect and Information Exposure. Titles that state access include Unauthenticated ones and Authenticated ones marked Subscriber+, Contributor+, Author+, Custom Role+, Admin+ or Administrator+.
- CVE-2026-96564, whose title ends "Unauthenticated Stored Cross-Site Scripting via Author Display Name": all versions up to and including 10.2, patched in 10.3.
- CVE-2026-116535, whose title ends "Authenticated (Subscriber+) Stored Cross-Site Scripting via 'display_name' Profile Field via %%archive_title%% Template Tag": all versions up to and including 10.3, patched in 10.4.
- CVE-2026-120515, whose title ends "Authenticated (Subscriber+) Stored Cross-Site Scripting via 'seopress_google_analytics_affiliate_tracking' and 'seopress_google_analytics_download_tracking' Parameters": all versions up to and including 10.3, patched in 10.4.
- CVE-2024-1168, whose title ends "Authenticated(Contributor+) Stored Cross-Site Scripting via Social Image URL": all versions up to and including 7.9, patched in 7.9.1.
- CVE-2024-5488, whose title ends "Unauthenticated PHP Object Injection": all versions up to and including 7.8, patched in 7.9.
SEOPress affected versions: match the fields, not the title
Match on each record's affected range and patched versions field, because titles repeat. CVE-2024-50454, CVE-2024-50455 and CVE-2024-50456 share a title ending "Missing Authorization" and the same affected range and patched versions field, all versions up to and including 8.1.1 with 8.2 as patched: tell them apart by CVE id.
A range can stop short of its patch. The range of CVE-2026-96564 ends at 10.2 and it lists 10.3 as patched, and the vendor's changelog shows a release between those two. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
Where each SEOPress check sits in the dashboard
The listing says a feature can be disabled in one click.
Leave every switch where it is and save nothing. The listing also says white label can replace the plugin name, logo, links and screens, so the SEO menu these steps use may carry another label.
The Plugins screen gives the installed version in each row's Description column. The vendor's get-started guide says the Free version is also required to use SEOPress PRO, so a PRO site has two rows to write down.
On PRO, the vendor's licence guide says a correct key shows a green "active" status on the SEO, License page. Read the status only: the guide says not to save changes there after activation.
The listing calls SEOPress modular, and the vendor's sitemap, Matomo and capabilities guides each include a step that switches the feature on from its own page (the capabilities guide calls it a module). Open each page under SEO and note whether its switch is on. The listing says a disabled feature keeps its settings, so read those too.
Under SEO, Analytics, copy what the Custom Tracking tab's two additional tracking code fields hold, one for the head and one for the body. Record titles name parameters beginning seopress_google_analytics, and say nothing about a screen. As this page's own check, also copy the download extensions and affiliate keywords under Google Analytics, Events, and the Matomo tab's tracking ID and site ID.
On the Advanced tab under SEO, Advanced, look for Expose abilities to AI agents and external tools and note whether it is on. If it is, the MCP tab lists the exposed tools and each connected client, approved for reading only or for reading and changing. The vendor's MCP guide says each user sees only their own connections, so each account that connected a client has to read its own.
On the XML and HTML sitemap page under SEO, where the vendor's sitemap guide starts, record whether Enable XML Sitemap is checked and what is checked on the Post Types and Taxonomies tabs: by default, the guide says, the sitemap contains posts, pages, products and post categories, if available. Then open /sitemaps.xml/ on the site's address, as the guide gives it, and list each sitemap it links.
The listing counts authors among the free XML sitemaps, and WordPress notes that an author's username is often included in the URL of their author archive, so copy any author URLs listed.
Under SEO, Titles & Metas, read the templates on each tab and copy any that use a variable a user fills in. The vendor's titles guide lists %%post_author%% as the post author's display name and %%archive_title%% as the archive title as WordPress names the current archive, alongside author biography, custom field and author user meta variables. Its author archives guide puts author templates on the Archives tab, in the Author archives section.
Then, logged out, view the source of a post and an author archive, and save the title, meta description and Open Graph tags as served.
Copy SEO, Advanced, Security in full. The vendor's capabilities guide says its checkboxes work in opposite directions: in the settings pages section a checked role is allowed, while in the SEO metabox and Content Analysis sections a checked role is blocked from editing that metabox. Note any role-management plugin too, which the guide's troubleshooting list says to check.
Then use the role filter links on the Users screen to see which accounts hold each allowed role. Some titles say Subscriber+. As this page's own check, record under Settings > General whether Anyone can register is ticked and the New User Default Role. On PRO, check wp-config.php for SEOPRESS_BLOCK_ROBOTS and SEOPRESS_BLOCK_HTACCESS, which the vendor documents as blocking robots.txt and .htaccess editing from the SEO, PRO screens.
SEOPress security questions a version match leaves open
No version field says which roles the Security tab admits, what the tracking code fields hold, which templates print a display name or a custom field, whether abilities are exposed to outside clients, or whether a PRO site blocks its robots.txt and .htaccess editors.
Matching a version tells you whether a known record covers that copy of SEOPress, and nothing about whether the site was attacked.
Two tests in a WordPress security audit sit close to the SEOPress titles that say Subscriber+ or name an author display name. Where Settings > General lets anyone register, the audit confirms that a new sign-up lands in the default role you chose and cannot pick a higher one. Logged out, it records which usernames and user slugs a visitor can see through author archive URLs.
Frequently asked questions
Compare the installed version with the affected range and patched versions field of every record in the history on this page. Not all are ranges: CVE-2021-34641, whose title ends "Stored Cross-Site Scripting", lists versions 5.0.0, 5.0.1, 5.0.2 and 5.0.3 one by one, with 5.0.4 as patched.
WordPress displays an update notice on the Plugins screen for a plugin hosted in its Plugin Directory when a newer version is available. Set the installed version against the update guidance at the top of the history too. For SEOPress PRO, the vendor's licence guide says a validated licence is needed to receive future updates. Before updating, read the vendor's Free and PRO changelog, which marks security work with lines such as "INFO Security hardening". The WordPress.org listing shows the entry for the listed release.
Every record on this page is one the source data files under wp-seopress, the slug of the WordPress.org plugin. Where a record is filed cannot show whether it also applies to SEOPress PRO or SEOPress Insights. The vendor's get-started guide says the Free version is also required to use SEOPress PRO, so a PRO site has both versions to write down. The vendor keeps one changelog for SEOPress Free and PRO and links to a separate one for SEOPress Insights.
The vendor's MCP guide says the built-in MCP server, included since version 10.3, is off by default: nothing is exposed until the abilities setting on the Advanced tab is turned on. Once on, the guide says, a connection acts as the WordPress account that approved it. Its Connected clients list shows OAuth connections only, and a client that signs in with an Application Password is revoked from the WordPress profile.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to every record listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- SEOPress <= 10.3 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'seopress_google_analytics_affiliate_tracking' and 'seopress_google_analytics_download_tracking' Parameters (CVE-2026-120515)
- SEOPress - AI SEO Plugin & On-site SEO < 10.4 - Authenticated (Custom Role+) Stored Cross-Site Scripting (CVE-2026-108041)
- SEOPress <= 10.3 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'display_name' Profile Field via %%archive_title%% Template Tag (CVE-2026-116535)
- SEOPress <= 10.2 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'seopress_google_analytics_matomo_id' Parameter (CVE-2026-101357)
- SEOPress <= 10.2 - Unauthenticated Stored Cross-Site Scripting via Author Display Name (CVE-2026-96564)
- SEOPress - AI SEO Plugin & On-site SEO <= 10.1 - Authenticated (Contributor+) Server-Side Request Forgery (CVE-2026-85305)
- SEOPress <= 8.1.1 - Missing Authorization (CVE-2024-50455)
- SEOPress <= 8.1.1 - Missing Authorization (CVE-2024-50454)
- SEOPress <= 8.1.1 - Missing Authorization (CVE-2024-50456)
- SEOPress - On-site SEO <= 8.1.1 - Reflected Cross-Site Scripting (CVE-2024-9225)
- SEOPress - On-site SEO <= 7.9 - Authenticated(Contributor+) Stored Cross-Site Scripting via Social Image URL (CVE-2024-1168)
- SEOPress <= 7.8 - Unauthenticated PHP Object Injection (CVE-2024-5488)
- SEOPress <= 7.7.2 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2024-4899)
- SEOPress <= 7.7.2 - Authenticated (Contributor+) Open Redirect (CVE-2024-4900)
- SEOPress - On-site SEO <= 7.5.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2024-1134)
- SEOPress <= 7.6.1 - Information Exposure (CVE-2024-34383)
- SEOPress - On-site SEO <= 7.5.2.1 - Authenticated (Author+) Stored Cross-Site Scripting (CVE-2024-2165)
- SEOPress - On-site SEO <= 7.2 - Authenticated (Admin+) Stored Cross-Site Scripting (CVE-2023-6290)
- SEOPress <= 6.5.0.2 - Authenticated (Administrator+) PHP Object Injection (CVE-2023-1669)
- SEOPress 5.0.0 - 5.0.3 - Stored Cross-Site Scripting (CVE-2021-34641)