# CVE-2010-2513: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the view parameter in the JE Ajax Event Calendar component for Joomla!.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5rwf-hpx5-32g3

## What is CVE-2010-2513?

CVE-2010-2513 is a high-severity SQL injection vulnerability in n/a, published on 28 Jun 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in the JE Ajax Event Calendar (com_jeajaxeventcalendar) component 1.0.5 for Joomla! allows remote attackers to execute arbitrary SQL commands via the view parameter to index.php.

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

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

It affects 1 product.


Products: Harmistechnology Com Jeajaxeventcalendar.

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

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

## Is CVE-2010-2513 being exploited?

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

Public exploit code:

- Joomla! Component JE Ajax Event Calendar 1.0.5 - SQL Injection (exploitdb)
- Joomla! Component JE Ajax Event Calendar - SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-4365](https://insights.sbomify.com/CVE-2010-4365/): SQL injection in n/a (high 7.5)
- [CVE-2010-2129](https://insights.sbomify.com/CVE-2010-2129/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2513 is a high-severity SQL injection vulnerability in n/a, published on 28 Jun 2010. 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-2010-2513 in the wild and no public exploit code.

Affected product: n/a. 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-2513/ (Markdown: https://insights.sbomify.com/CVE-2010-2513/index.md)
```

## Sources

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

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