# CVE-2024-49246: WordPress Ajax Rating with Custom Login plugin <= 1.1 - SQL Injection vulnerability

> An SQL injection vulnerability in the Ajax Rating with Custom Login WordPress plugin allows attackers to read or modify database contents.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2024
- **Updated:** 12 May 2026
- **Also known as:** GHSA-64wj-w5hh-h98q

## What is CVE-2024-49246?

CVE-2024-49246 is a critical SQL injection vulnerability in anand23 Ajax Rating with Custom Login, published on 17 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in anand23 Ajax Rating with Custom Login ajax-rating-with-custom-login allows SQL Injection.This issue affects Ajax Rating with Custom Login: from n/a through <= 1.1.

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

## Which versions are affected by CVE-2024-49246?


## How do I fix CVE-2024-49246?

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

## Is CVE-2024-49246 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49246 and fix it if it is affected.

What it is: CVE-2024-49246 is a critical SQL injection vulnerability in anand23 Ajax Rating with Custom Login, published on 17 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-49246 in the wild and no public exploit code.

Affected product: anand23 Ajax Rating with Custom Login. 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-2024-49246/ (Markdown: https://insights.sbomify.com/CVE-2024-49246/index.md)
```

## Sources

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

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