Dynamic Year and Copyright Shortcode Security & Risk Analysis

wordpress.org/plugins/dynamic-copyright-year-and-shortcode

This plugins allows you to keep the Copyright year of the website always updated.

300 active installs v0.1 PHP + WP 3.0.1+ Updated Jan 30, 2018
automatic-copyright-yearcopyright-shortcodedynamic-copyright-yearupdated-copyright-yearyear-shortcode
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Dynamic Year and Copyright Shortcode Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 8yr ago
Risk Assessment

The "dynamic-copyright-year-and-shortcode" plugin, version 0.1, demonstrates a generally good security posture based on the provided static analysis. The absence of dangerous functions, external HTTP requests, file operations, and the use of prepared statements for all SQL queries are positive indicators. Furthermore, 100% of outputs are properly escaped, and no taint analysis revealed any unsanitized paths.

However, there are significant areas of concern stemming from the lack of security checks. The plugin has three shortcodes, which represent entry points into the application, yet none have capability checks or nonce verification. While the attack surface is small and there are no reported CVEs, this omission creates a potential weakness. Any functionality exposed through shortcodes without proper authentication or authorization can be exploited by authenticated users, or in some cases, even unauthenticated users if the shortcode output is directly accessible or can be manipulated.

Given the minimal feature set and lack of complex operations, the vulnerability history of zero CVEs is expected. The plugin's strengths lie in its clean code practices regarding SQL and output handling. The primary weakness is the lack of any access control on its shortcode entry points, which, despite the small attack surface, represents a direct security oversight.

Key Concerns

  • Shortcodes lack capability checks
  • Shortcodes lack nonce checks
Vulnerabilities
None known

Dynamic Year and Copyright Shortcode Security Vulnerabilities

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

Dynamic Year and Copyright Shortcode 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

Dynamic Year and Copyright Shortcode Attack Surface

Entry Points3
Unprotected0

Shortcodes 3

[current_year] dynamic-copyright-year-shortcode.php:46
[current_year_with_copyright_symbol] dynamic-copyright-year-shortcode.php:65
[current_year_with_copyright_symbol_and_title] dynamic-copyright-year-shortcode.php:85
WordPress Hooks 1
actionplugins_loadeddynamic-copyright-year-shortcode.php:18
Maintenance & Trust

Dynamic Year and Copyright Shortcode Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedJan 30, 2018
PHP min version
Downloads9K

Community Trust

Rating64/100
Number of ratings5
Active installs300
Developer Profile

Dynamic Year and Copyright Shortcode Developer Profile

Deepak Kumar Vellingiri

1 plugin · 300 total installs

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

How We Detect Dynamic Year and Copyright Shortcode

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
dcywrapperdcycontainerdcyitem
Shortcode Output
<div class="dcywrapper"><div class="dcycontainer"><span class=="dcyitem"><div class="dcywrapper"><div class="dcycontainer"><span class=="dcyitem">&copy <div class="dcywrapper"><div class="dcycontainer"><span class=="dcyitem">
FAQ

Frequently Asked Questions about Dynamic Year and Copyright Shortcode