# CVE-2022-0785: Daily Prayer Time < 2022.03.01 - Unauthenticated SQLi

> Unauthenticated attackers can exploit SQL injection in the Daily Prayer Time plugin to read or modify database contents.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9qv2-4g99-78c9

## What is CVE-2022-0785?

CVE-2022-0785 is a critical SQL injection vulnerability in Unknown Daily Prayer Time, published on 18 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Daily Prayer Time WordPress plugin before 2022.03.01 does not sanitise and escape the month parameter before using it in a SQL statement via the get_monthly_timetable AJAX action (available to unauthenticated users), leading to an unauthenticated SQL injection

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

## Which versions are affected by CVE-2022-0785?

It affects 1 product.


Products: Daily Prayer Time Project Daily Prayer Time.

## How do I fix CVE-2022-0785?

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

## Is CVE-2022-0785 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0785 exists.

Public exploit code:

- WordPress Daily Prayer Time <2022.03.01 - SQL Injection (nuclei): http/cves/2022/CVE-2022-0785.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0785 and fix it if it is affected.

What it is: CVE-2022-0785 is a critical SQL injection vulnerability in Unknown Daily Prayer Time, published on 18 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0785 exists.

Affected product: Unknown Daily Prayer Time. 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-2022-0785/ (Markdown: https://insights.sbomify.com/CVE-2022-0785/index.md)
```

## Sources

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

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