# CVE-2025-9519: Easy Timer <= 4.2.1 - Authenticated (Editor+) Remote Code Execution via Shortcode

> Authenticated editors can execute arbitrary code on the server via insufficiently restricted shortcode attributes in the Easy Timer WordPress plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-c888-6x8j-w743

## What is CVE-2025-9519?

CVE-2025-9519 is a high-severity code injection vulnerability in kleor Easy Timer, published on 4 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-9519?


## How do I fix CVE-2025-9519?

No fix has been published for CVE-2025-9519 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-9519 being exploited?

There is no known exploitation of CVE-2025-9519 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Nimisha17/Poc-CVE-2025-9519 (github_poc): https://github.com/Nimisha17/Poc-CVE-2025-9519

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9519 and fix it if it is affected.

What it is: CVE-2025-9519 is a high-severity code injection vulnerability in kleor Easy Timer, published on 4 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9519 in the wild and no public exploit code.

Affected product: kleor Easy Timer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9519/ (Markdown: https://insights.sbomify.com/CVE-2025-9519/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9519
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9519
- OSV: https://osv.dev/vulnerability/CVE-2025-9519

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9519/
Summaries are generated and may contain mistakes; the official description above is the record.