Automatic Copyright Year Security & Risk Analysis

wordpress.org/plugins/automatic-copyright-year

Automatic Copyright Year seeks to solve a common problem: keeping your copyright year up-to-date.

7K active installs v1.1 PHP + WP 3.0.1+ Updated Jul 22, 2019
copyrightcopyright-yearfooter-copyrightshortcodewidget
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Automatic Copyright Year Safe to Use in 2026?

Generally Safe

Score 85/100

Automatic Copyright Year has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 6yr ago
Risk Assessment

The "automatic-copyright-year" plugin version 1.1 demonstrates a strong security posture based on the provided static analysis. The code utilizes prepared statements for all SQL queries and properly escapes all output, indicating good practices in preventing common web vulnerabilities like SQL injection and XSS. Furthermore, there are no detected dangerous functions, file operations, external HTTP requests, or indications of unsanitized taint flows, which are all positive signs for security. The plugin also has a clean vulnerability history, with no known CVEs recorded, further reinforcing its secure design.

While the plugin appears robust, there is a single shortcode identified as an entry point. Although the static analysis reports no unprotected entry points and no specific capability checks or nonce checks are explicitly mentioned for this shortcode, this represents a potential area for future scrutiny if the shortcode's functionality were to become more complex or involve user-supplied data. However, based solely on the provided data, this shortcode is not currently presenting an immediate risk. The absence of any identified vulnerabilities or concerning code signals suggests the developers have followed secure coding guidelines. Overall, this plugin exhibits a very good security profile with no immediate or apparent significant risks detected.

Vulnerabilities
None known

Automatic Copyright Year Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

Automatic Copyright Year 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
Attack Surface

Automatic Copyright Year Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[wpsos_year] automatic-copyright-year.php:50
WordPress Hooks 2
filterwidget_textautomatic-copyright-year.php:31
actionwp_enqueue_scriptsautomatic-copyright-year.php:40
Maintenance & Trust

Automatic Copyright Year Maintenance & Trust

Maintenance Signals

WordPress version tested5.2.24
Last updatedJul 22, 2019
PHP min version
Downloads30K

Community Trust

Rating86/100
Number of ratings9
Active installs7K
Developer Profile

Automatic Copyright Year Developer Profile

Miina Sikk

9 plugins · 8K total installs

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

How We Detect Automatic Copyright Year

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/automatic-copyright-year/script.js
Script Paths
/wp-content/plugins/automatic-copyright-year/script.js
Version Parameters
automatic-copyright-year/script.js?ver=1.0

HTML / DOM Fingerprints

Shortcode Output
[wpsos_year]
FAQ

Frequently Asked Questions about Automatic Copyright Year