Last-Modified and If-Modified-Since Headers Security & Risk Analysis

wordpress.org/plugins/last-modified-and-if-modified-since-headers

Add Last-Modified anв support If-Modified-Since Headers

200 active installs v1.0 PHP + WP 5.2.4+ Updated Jul 20, 2021
headersif-modified-sincelast-modified
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Last-Modified and If-Modified-Since Headers Safe to Use in 2026?

Generally Safe

Score 85/100

Last-Modified and If-Modified-Since Headers has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 4yr ago
Risk Assessment

The 'last-modified-and-if-modified-since-headers' plugin v1.0 exhibits an excellent security posture based on the provided static analysis. The complete absence of any identified attack surface points, including AJAX handlers, REST API routes, shortcodes, and cron events, indicates a highly contained and well-defined functionality. Furthermore, the code signals are overwhelmingly positive, with no dangerous functions, all SQL queries using prepared statements, and all output properly escaped. The plugin also avoids file operations, external HTTP requests, and correctly uses nonces and capability checks where applicable.

Despite the strong static analysis, the taint analysis reveals two flows with unsanitized paths. While these are not classified as critical or high severity, they warrant attention as they represent potential vectors for unexpected behavior or data manipulation if the plugin's inputs are not strictly controlled. The lack of any historical vulnerabilities is a significant strength, suggesting consistent security focus from the developers. However, the absence of historical data also means there's no track record to review for past issues and their resolutions, which is a minor point to consider.

In conclusion, this plugin appears to be very secure due to its minimal attack surface and robust coding practices. The primary area for improvement lies in addressing the identified taint flows, even if they are currently low severity, to ensure complete sanitization of all data paths.

Key Concerns

  • Flows with unsanitized paths found
Vulnerabilities
None known

Last-Modified and If-Modified-Since Headers Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Last-Modified and If-Modified-Since Headers Release Timeline

No version history available.
Code Analysis
Analyzed Mar 16, 2026

Last-Modified and If-Modified-Since Headers Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
0
0 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0
Data Flows · Security
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
last_if_modified_headers (last-modified-and-if-modified-since-headers.php:17)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Last-Modified and If-Modified-Since Headers Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwplast-modified-and-if-modified-since-headers.php:15
Maintenance & Trust

Last-Modified and If-Modified-Since Headers Maintenance & Trust

Maintenance Signals

WordPress version tested5.7.15
Last updatedJul 20, 2021
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings2
Active installs200
Developer Profile

Last-Modified and If-Modified-Since Headers Developer Profile

zubovd

1 plugin · 200 total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Last-Modified and If-Modified-Since Headers

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Last-Modified and If-Modified-Since Headers