CVE-2026-116535 rainbowgeek CVE debrief

Who should care

Defenders responsible for WordPress installations with the SEOPress plugin should assess exposure and prioritize verification and potential updates. This includes security teams, vulnerability management teams, and operators who manage WordPress deployments. They should review the CVE record and NVD entry for details on the vulnerability and its potential impact.

Why it matters

The SEOPress plugin vulnerability allows authenticated attackers to inject arbitrary web scripts, which can lead to Stored Cross-Site Scripting attacks. Defenders should prioritize verifying and updating the plugin, monitoring for exploitation attempts, and adjusting input sanitization and output escaping.

• Authenticated attackers with subscriber-level access and above can inject arbitrary web scripts
• Injected scripts execute when a user accesses an injected page
• Defenders must verify and update the SEOPress plugin to a fixed version, if available
• Defenders should monitor for potential exploitation attempts

Technical summary

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.

Defensive priority

Defenders should prioritize verifying and updating the SEOPress plugin to a fixed version, if available, and monitor for potential exploitation attempts.

Recommended defensive actions

• Verify and update the SEOPress plugin to a fixed version, if available
• Monitor for potential exploitation attempts
• Review and adjust the display_name parameter input sanitization and output escaping
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. The vulnerability is caused by insufficient input sanitization and output escaping in the 'display_name' parameter. The CVE Program and NVD entries provide evidence of the vulnerability and its potential impact. Defenders should verify the affected versions and assess exposure. The evidence is limited to public CVE and NVD records, and defenders may need to conduct further verification.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.