# CVE-2021-24553: Timeline Calendar <= 1.2 - Authenticated (admin+) SQL Injection

> Authenticated administrators can exploit SQL injection in the Timeline Calendar plugin to read or modify database contents.

- **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:** 23 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2qx4-67q8-fwg5

## What is CVE-2021-24553?

CVE-2021-24553 is a high-severity SQL injection vulnerability in Unknown Timeline Calendar, published on 23 Aug 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Timeline Calendar WordPress plugin through 1.2 does not sanitise, validate or escape the edit GET parameter before using it in a SQL statement when editing events, leading to an authenticated SQL injection issue. Other SQL Injections are also present in the plugin

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2021-24553?

It affects 1 product.


Products: Timeline Calendar Project Timeline Calendar.

## How do I fix CVE-2021-24553?

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

## Is CVE-2021-24553 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24553 and fix it if it is affected.

What it is: CVE-2021-24553 is a high-severity SQL injection vulnerability in Unknown Timeline Calendar, published on 23 Aug 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24553 in the wild and no public exploit code.

Affected product: Unknown Timeline Calendar. 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-2021-24553/ (Markdown: https://insights.sbomify.com/CVE-2021-24553/index.md)
```

## Sources

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

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