We’re actively acquiring WordPress agencies. Sell your WordPress business to Freshy.
Let’s discuss

WordPress Security Bulletin: Countdown Timer 6 Widget Countdown Plugin Vulnerability (CVE-2025-14555)

Nick Paliughi
On this page

Security Alert Summary

The Countdown Timer 6 Widget Countdown plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability via the plugin’s wpdevart_countdown shortcode. Insufficient input sanitization and output escaping of user-supplied shortcode attributes allow authenticated users with contributor-level access and above to inject scripts that will execute when an injected page is viewed.

CVE Details

  • CVE ID: CVE-2025-14555
  • Affected plugin / component: The Countdown Timer 6 Widget Countdown plugin for WordPress
  • Affected versions: All versions up to, and including, 2.7.7
  • Published: January 10, 2026 at 1:15:48 PM (timestamp from CVE)
  • Last modified: January 10, 2026 at 1:15:48 PM (timestamp from CVE)
  • CVSS v3.1: Base Score 6.4, Severity MEDIUM
    • Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
    • Attack Vector: NETWORK
    • Attack Complexity: LOW
    • Privileges Required: LOW (authenticated contributor-level access and above)
    • User Interaction: NONE
    • Scope: CHANGED
  • Primary impact: Confidentiality: LOW; Integrity: LOW; Availability: NONE
  • CWE / Weakness ID: CWE-79
  • Fixed version: Not specified in the CVE entry

Technical Details

The vulnerability is a stored cross-site scripting (XSS) issue arising from insufficient input sanitization and missing output escaping for attributes provided to the wpdevart_countdown shortcode. According to the CVE description, user-supplied attributes are not properly validated or escaped before being rendered, allowing attackers with contributor-level privileges or higher to persist arbitrary HTML/JavaScript inside pages that include the shortcode.

The CVE references implementation code paths under includes/front_end.php, which indicate where shortcode output is constructed and returned. Because the injected script is stored in page content or shortcode attributes, the payload will execute in the context of any visitor or authenticated user who views the affected page.

Impact is limited to the effects typical of stored XSS: attacker-controlled script execution in victims’ browsers. The CVSS metrics indicate low confidentiality and integrity impacts and no availability impact, which aligns with the vulnerability allowing limited data disclosure or unauthorized actions within the scope of a victim’s browser session rather than guaranteed system takeover.

How This Could Impact Your Website

Consider a site where the site owner manages content and several contributors (including external contractors) can create or edit pages. An attacker who has contributor-level access could insert malicious JavaScript into a countdown shortcode attribute when creating or editing a page or widget. When another user—such as an editor, administrator, or regular site visitor—views that page, the script runs in their browser.

Practical consequences may include exposure of information accessible in the browser context (for example, session tokens or form data), content manipulation visible to users, or facilitating targeted social engineering. Given the CVSS impact ratings, these effects are assessed as limited (confidentiality and integrity impacts are LOW and availability is NONE), but they can still enable effective targeted phishing or unauthorized actions performed with the victim’s privileges.

If you’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review your setup.

Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor accounts that can submit content with shortcodes.
  • Enforce strong passwords and two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from your site.
  • Monitor site activity and logs for unusual behavior, such as unexpected shortcode content or new pages created by lower-privileged users.

If you’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.

References

Nick Paliughihttps://freshysites.com/team/nick-paliughi/
Nick was born in California and now resides in Lake Worth, FL. He has 10 years of experience building and maintaining sites in WordPress, which he is excited to put to use at Freshy. Prior to starting at Freshy in 2022 his focus was on WordPress security & malware removal. When he’s not tending to your website, Nick is installing exhibitions at art galleries and museums in Palm Beach County, and if he’s lucky surfing at the Lake Worth pier.

See our featured website design work

Check out some of the beautiful websites we’ve built for over 2,000 clients.

View projects

We offer WordPress support & maintenance

Shake the stress of ongoing maintenance with plans supported by our team of WordPress experts.

Learn more
Previous Post
WordPress Security Bulletin: The User Registration & Membership 6 Custom Registration Form Builder, Custom Login Form, User Profile, Content Restriction & Membership Plugin plugin (CVE-2025-14976)
Next Post
WordPress Security Bulletin: Dreamer Blog WordPress theme Vulnerability (CVE-2025-10915)