Plugins · hostinger-reach · data as of 2026-11-01
Is Hostinger Reach safe? Known vulnerabilities and latest version
- Latest version
- 1.8.7
- Last updated
- 2026-10-14
- Active installs
- 1+ million
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 8.1+
Launch and grow your email marketing effortlessly with Hostinger Reach. Collect contacts, sync subscribers, and send emails – all in one, AI powered. — by Hostinger
What to do
- Update to the latest version (1.8.7). Anything older than 1.8.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get hostinger-reach --field=version shows what you run; wp plugin update hostinger-reach updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.8 CVE-2026-87777 · published 2026-09-30
Cross-site scripting (XSS) in Hostinger Reach (1.0.6 up to (not including) 1.8.3)
- Affected
- 1.0.6 up to (not including) 1.8.3
- Fixed in
- 1.8.3
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Hostinger Reach WordPress plugin before 1.8.3 does not sanitize and escape a widget setting before outputting it in the editor preview, allowing users with contributor-level access and above to inject arbitrary web scripts that will execute in the session of a higher-privileged user who opens the affected content in the editor.
medium 5.3 CVE-2026-2515 · published 2026-05-13
Missing authorization check in Hostinger Reach (1.3.8 and older)
- Affected
- 1.3.8 and older
- Fixed in
- 1.3.9 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-2515Wordfence advisoryCode change (fix)Plugin source
Recent activity
- 2026-10-14 — latest release on wordpress.org (1.8.7).
- 2026-09-30 — Cross-site scripting (XSS) disclosed (CVE-2026-87777), fixed in 1.8.3.
- 2026-05-13 — Missing authorization check disclosed (CVE-2026-2515), fixed in 1.3.9.
Get an email when Hostinger Reach has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Hostinger Reach (hostinger-reach) is published or a fix ships. Unsubscribe in one click.
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/hostinger-reach (Plugins API), fetched 2026-11-01.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-01. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/hostinger-reach"><img src="https://laskyr.com/plugins/hostinger-reach/badge.svg" alt="Hostinger Reach vulnerability status"></a>