dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-9519

HIGH · 7.2 CVSS v3.1 Published 2025-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Easy Timer plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.2.1 via the plugin's shortcodes. This is due to insufficient restriction of shortcode attributes. This makes it possible for authenticated attackers, with Editor-level access and above, to execute code on the server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Easy Timer WordPress plugin versions up to 4.2.1 contain a Remote Code Execution vulnerability in its shortcode functionality. Due to insufficient restriction of shortcode attributes, authenticated users with Editor-level access or higher can execute arbitrary code on the server through maliciously crafted shortcode parameters.

MitigationUpdate the Easy Timer plugin to a version beyond 4.2.1 once a patch is released. If no patch is available, remove the plugin or implement temporary compensating controls such as restricting the Editor role capabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Easy Timer plugin is installed
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins. Look for 'Easy Timer' in the list of active or inactive plugins.
    Affected if The Easy Timer plugin is present in the plugins directory regardless of activation status, as even inactive plugins may retain exploitable code.
  2. Determine installed Easy Timer version
    In the plugins list, find the Easy Timer entry. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (e.g., /wp-content/plugins/easy-timer/easy-timer.php) and look for the 'Version' header comment.
    Affected if The installed version is 4.2.1 or any version prior to it (e.g., 4.2.0, 4.1.x, 4.0.x).
  3. Confirm shortcode functionality is accessible
    Verify the plugin is active in the WordPress admin. Shortcodes are processed when the plugin is enabled. Check for the presence of the shortcode handler in the plugin files (look for 'add_shortcode' function calls in the plugin code).
    Affected if The Easy Timer plugin is active and the shortcode handler is registered and processing user input.
  4. Inspect shortcode usage patterns
    Review posts, pages, and widget content where the [easy_timer] shortcode may be used. Look for any shortcode with unusual attribute patterns that could indicate exploitation attempts.
    Affected if Shortcode attributes are being processed without proper sanitization, allowing injection of malicious parameters.

Your environment is affected if the Easy Timer plugin is installed with version 4.2.1 or lower and the shortcode functionality is active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Easy Timer plugin to a version beyond 4.2.1 once a patch is released. If no patch is available, remove the plugin or implement temporary compensating controls such as restricting the Editor role capabilities.

Recommended fix High confidence

Version 4.2.2 or later (upgrade from 4.2.1 or earlier)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Easy Timer plugin
  4. Click 'Update now' if an update is available, or manually upload version 4.2.2 or higher from the WordPress plugin repository
  5. Verify the update was successful by checking the plugin version
Caveat Review plugin settings and any custom shortcode implementations after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9519 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data