XO Security · Security record
Is XO Security safe?
No known vulnerability affects the current version (3.11.0). 2 issues were found in earlier versions and fixed, the latest disclosed on Feb 7, 2017.
Checked 3 days ago against the WPVulnerability database, for version 3.11.0.
How it’s looked after
- Last release
- Jul 19, 2026 (3 months ago)
- Releases in the last year
- 6
- Tested up to
- WordPress 7.0.8
- Active installs
- 30K+
2 known vulnerabilities
- 1 medium
- 1 not rated
None affects the current version.
Every known vulnerability in XO Security
Newest first, with any that affect the current version at the top.
Fixed in 1.5.3 · Feb 7, 2017 · Patchstack
- medium
Cross-Site Scripting
Fixed in 1.5.3 · CVE-2017-18541 · Feb 7, 2017 · Wordfence
Questions about XO Security’s security
Is XO Security safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep XO Security updated: most attacks target sites that haven’t updated.
Does XO Security have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep XO Security up to date.
Is XO Security still maintained?
Yes. Its last release was 3 months ago. No support threads were opened in the last two months.
Is XO Security compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
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 freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.