Is Hostinger Reach safe?

No known vulnerability affects the current version (1.8.8). 2 issues were found in earlier versions and fixed, the latest disclosed on Sep 30, 2026.

Checked 3 days ago against the WPVulnerability database, for version 1.8.8.

How it’s looked after

Last release: Nov 4, 2026 (4 days ago)
Releases in the last year: 47
Tested up to: WordPress 7.1.4
Active installs: 1M+

2 known vulnerabilities

1 medium
1 not rated

None affects the current version.

Every known vulnerability in Hostinger Reach

Newest first, with any that affect the current version at the top.

Cross-site Scripting
Fixed in 1.8.3 · CVE-2026-87777 · Sep 30, 2026 · CVE
medium
Missing Authorization to Authenticated (Subscriber+) Integration API Key Update
Fixed in 1.3.9 · CVE-2026-2515 · May 12, 2026 · Wordfence

Questions about Hostinger Reach’s security

Is Hostinger Reach safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Hostinger Reach updated: most attacks target sites that haven’t updated.

Does Hostinger Reach have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep Hostinger Reach up to date.

Is Hostinger Reach still maintained?

Yes. Its last release was 4 days ago. No support threads were opened in the last two months.

Is Hostinger Reach compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.