Hostinger Reach <= 1.3.8 - Missing Authorization to Authenticated (Subscriber+) Integration API Key Update
Strategic Overview
- Status
- Patched in 1.3.9
- Affected Plugin
- Hostinger Reach – AI-Powered Email Marketing for WordPress
- Affected Version
<= 1.3.8- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-2515
At a glance
CVE-2026-2515 is a medium-severity Missing Authorization vulnerability in the Hostinger Reach WordPress plugin, affecting versions <= 1.3.8. It carries a CVSS score of 5.3 (reachable over the network; high integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.3.9; sites on affected versions should update now. Disclosed May 2026, reported by Dmitrii Ignatyev.
Vulnerability Overview
The Hostinger Reach – AI-Powered Email Marketing for WordPress plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'handle_ajax_action' function in all versions up to, and including, 1.3.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to use the 'hostinger_reach_connection_notice_action' action to update the API key value stored in the database. This vulnerability can only be exploited when the plugin is not connected to a site and no API key value exists in the database.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Hostinger Reach <= 1.3.8 carries this weakness at handle_ajax_action, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Hostinger Reach the fix is 1.3.9: builds <= 1.3.8 are affected, anything from 1.3.9 onward is not.
Remediation
Update to version 1.3.9, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Hostinger Reach 1.3.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C