CVE-2026-115214 Datawiza CVE debrief

Who should care

Defenders responsible for WordPress installations with the Datawiza Proxy Auth Plugin should assess exposure and prioritize verification of the plugin version. Additionally, vulnerability management teams and security operators should be aware of the potential risks associated with this vulnerability and take necessary steps to mitigate them. Platform administrators and security teams should also review their current configurations and implement compensing

Why it matters

Defenders should prioritize verifying the plugin version and assessing exposure, as the vulnerability allows unauthenticated attackers to create and authenticate as a WordPress administrator, potentially leading to authentication bypass attempts.

• Unauthenticated attackers can create and authenticate as a WordPress administrator
• Potential authentication bypass attempts require monitoring

Technical summary

The Datawiza Proxy Auth Plugin WordPress plugin before 1.1.1 does not verify that the user-identity and role HTTP request headers it trusts originate from a trusted reverse proxy. This vulnerability allows unauthenticated attackers to create and authenticate as a WordPress administrator. The technical issue lies in the plugin's failure to validate the origin of user-identity and role HTTP request headers, which can be exploited to bypass authentication mechanisms. Defenders should focus on verifying the plugin version and implementing additional security measures to mitigate potential risks.

Defensive priority

Defenders should prioritize verifying the plugin version and assessing exposure, as the vulnerability allows unauthenticated attackers to create and authenticate as a WordPress administrator.

Recommended defensive actions

• Verify the plugin version and assess exposure
• Implement trusted reverse proxy checks for user-identity and role HTTP request headers
• Monitor for potential authentication bypass attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD vulnerability detail page provide limited information about the vulnerability. The primary source being the WPScan reference. There is no explicit evidence of vendor guidance or patch availability. Defenders should verify the plugin version and assess exposure based on available information. Additional verification tasks may be necessary due to limited source detail.

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.