Ultimate 410 Gone Status Code

Ultimate 410 Gone Status Code has one disclosed vulnerability in the WordSec catalog, all reported in 2024; it is fixed as of September 2026. Their average CVSS score is 6.4, and the most serious one scores 6.4 out of 10.

The most common weakness is Cross-Site Scripting, behind 1 of the records (100%).

The one issue recorded for Ultimate 410 Gone Status Code has a vendor fix available, so running the current release closes it.

All of these findings were reported by Krzysztof Zając. Ultimate 410 Gone Status Code is installed on roughly 6,000 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 6.6.7.

Strategic Overview

Avg CVSSMedium
6.4/ 10
Patch Coverage100%
Open

0

Fixed

1

Get automatic notifications for all Ultimate 410 Gone Status Code vulnerabilities before they are exploited.

Highest severity on recordCVSS 6.4CVE-2024-3677

Ultimate 410 Gone Status Code <= 1.1.4 - Authenticated (Contributor+) Stored Cross-Site Scripting

Read the full analysis

Vulnerability Records

1 records
Ultimate 410 Gone Status Code banner
Latestv1.1.7

Ultimate 410 Gone Status Code

tiny web

Author

tiny web

4.4(8)
88/100
Last Updated
2024-08-15 (2y ago)
Active Installs
6,000+
Downloads
45,221
Requires WP
5.1+
Requires PHP
7.0+
Tested up to
WP 6.6.7
Created
2020-08-09 (6y ago)

In accordance with the HTTP Specification, the 410 status code in the response header indicates that the requested resource is gone (permanently removed). Features: When deleting pages, posts, categories or tags from WordPress, the ultimate 410 status code will ask if a 410 response code should be set for the deleted URL. Add 410 URLs manually Add 410 URL schemes via regex (regular expressions) Bulk upload 410 URLs via csv-file. works even if the csv-file contains a BOM If you come across any bugs or have suggestions, please use the plugin support forum.

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C