Ultimate 410 Gone Status Code

Explore Ultimate 410 Gone Status Code vulnerabilities across all versions. Currently tracking 1 known vulnerabilities, including severity, impact, and patch status.

Strategic Overview

Avg CVSSMedium

6.4/ 10

Patch Coverage100%

Open

Fixed

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

Vulnerability Records

1 records


2024-04-22 00:00	Ultimate 410 Gone Status Code <= 1.1.4 - Authenticated (Contributor+) Stored Cross-Site Scripting Ultimate 410 Gone Status Code <= 1.1.4	`CVE-2024-3677`	6.4 Medium	Krzysztof Zając	Yes

Showing 1–1 of 1 reports

Latestv1.1.7

Ultimate 410 Gone Status Code

Author

tiny web

4.4(8)

88/100

Last Updated

2024-08-15 (2y ago)

Active Installs

6,000+

Downloads

44,211

Requires WP

5.1+

Requires PHP

7.0+

Tested up to

WP 6.6.5

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.

View on WordPress.org