# CVE-2010-10007: lierdakil click-reminder BaseAction.php db_query sql injection

> SQL injection in click-reminder plugin allows attackers to manipulate database queries, risking data exposure or modification.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2023
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jc78-g8h5-qgrg

## What is CVE-2010-10007?

CVE-2010-10007 is a medium-severity SQL injection vulnerability in lierdakil click-reminder, published on 18 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in lierdakil click-reminder. It has been rated as critical. This issue affects the function db_query of the file src/backend/include/BaseAction.php. The manipulation leads to sql injection. The identifier of the patch is 41213b660e8eb01b22c8074f06208f59a73ca8dc. It is recommended to apply a patch to fix this issue. The identifier VDB-218465 was assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

## Which versions are affected by CVE-2010-10007?

It affects 1 product.


Products: Click-Reminder Project Click-Reminder.

## How do I fix CVE-2010-10007?

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

## Is CVE-2010-10007 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-10007 and fix it if it is affected.

What it is: CVE-2010-10007 is a medium-severity SQL injection vulnerability in lierdakil click-reminder, published on 18 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-10007 in the wild and no public exploit code.

Affected product: lierdakil click-reminder. 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-2010-10007/ (Markdown: https://insights.sbomify.com/CVE-2010-10007/index.md)
```

## Sources

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

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