Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

Ultimate 410 Gone Status Code · Security record

Is Ultimate 410 Gone Status Code safe?

No known vulnerability affects the current version (1.1.7). 1 issue was found in earlier versions and fixed, the latest disclosed on Apr 22, 2024.

Checked 5 days ago against the WPVulnerability database, for version 1.1.7.

How it’s looked after

Last release
Aug 15, 2024 (2 years ago)
Releases in the last year
0
Tested up to
WordPress 6.6.11 (current: 7.1)
Active installs
6K+

1 known vulnerability

  • 1 medium

None affects the current version.

Every known vulnerability in Ultimate 410 Gone Status Code

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

Questions about Ultimate 410 Gone Status Code’s security

Is Ultimate 410 Gone Status Code safe to use?

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

Does Ultimate 410 Gone Status Code have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Ultimate 410 Gone Status Code up to date.

Is Ultimate 410 Gone Status Code still maintained?

Its last release was 2 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.

Is Ultimate 410 Gone Status Code compatible with the latest WordPress?

Ultimate 410 Gone Status Code’s readme says it’s tested up to WordPress 6.6.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.

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.