CVE-2026-104643 Easy HTTPS Redirection (SSL) CVE debrief

Who should care

Defenders responsible for WordPress installations with the Easy HTTPS Redirection (SSL) plugin should assess exposure and prioritize verification and remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure the plugin is updated and access is restricted to prevent potential exploitation.

Why it matters

The Easy HTTPS Redirection (SSL) plugin vulnerability allows authenticated users to read and rewrite URLs, potentially impacting site security and data integrity.

• Authenticated users may be able to read sensitive URLs
• Site-wide URL rewrites may be triggered by authenticated users
• Defenders should verify the version of the plugin and restrict access to authenticated users

Technical summary

The Easy HTTPS Redirection (SSL) WordPress plugin before 2.0.2 does not perform capability checks in some of its AJAX actions, allowing any authenticated user, such as a Subscriber, to read URLs its content scanner collected from private and draft posts and from site options, and to trigger a site-wide rewrite of those URLs, once an administrator has run a scan. This vulnerability allows authenticated users to read and rewrite URLs, potentially impacting site security and data integrity. Defenders should prioritize verifying the version of the Easy HTTPS Redirection (SSL) plugin and restricting access to authenticated users.

Defensive priority

Defenders should prioritize verifying the version of the Easy HTTPS Redirection (SSL) plugin and restricting access to authenticated users.

Recommended defensive actions

• Verify the version of the Easy HTTPS Redirection (SSL) plugin and update to 2.0.2 or later.
• Restrict access to authenticated users and limit the scope of the plugin's AJAX actions.
• Monitor for potential exploitation and review site-wide URL rewrites.
• 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.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the vulnerability, but limited information is available on potential exploitation or impact. Defenders should verify the version of the Easy HTTPS Redirection (SSL) plugin and restrict or remove access to authenticated users. Monitor for potential exploitation and review site-wide URL rewrites. Consider compensating controls for exposed systems while remediation is scheduled and verified.

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.