# CVE-2018-1002000: SQL injection in Arigato Autoresponder and Newsletter

> Administrators can exploit blind SQL injection in the Arigato Autoresponder and Newsletter plugin to read or modify database contents.

- **Severity:** High 7.2 (`CVSS:3.0/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:** 3 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xhcp-hwcp-p5wq

## What is CVE-2018-1002000?

CVE-2018-1002000 is a high-severity SQL injection vulnerability in Kiboko Labs https://calendarscripts.info/ Arigato Autoresponder and Newsletter, published on 3 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

There is blind SQL injection in WordPress Arigato Autoresponder and Newsletter v2.5.1.8 These vulnerabilities require administrative privileges to exploit. There is an exploitable blind SQL injection vulnerability via the del_ids variable by POST request.

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

## Which versions are affected by CVE-2018-1002000?

It affects 1 product.


Products: Kibokolabs Arigato Autoresponder and Newsletter.

## How do I fix CVE-2018-1002000?

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

## Is CVE-2018-1002000 being exploited?

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

Public exploit code:

- WordPress Plugin Arigato Autoresponder and Newsletter 2.5 - Blind SQL Injection / Reflected Cross-Site Scripting (exploitdb)
- WordPress Plugin Arigato Autoresponder and Newsletter 2.5 - Blind SQL Injection / Reflected Cross-Site Scripting (exploitdb)

## Other vulnerabilities in Kiboko Labs https://calendarscripts.info/ Arigato Autoresponder and Newsletter

- [CVE-2018-18461](https://insights.sbomify.com/CVE-2018-18461/): Code injection in n/a (critical 9.8)
- [CVE-2023-25020](https://insights.sbomify.com/CVE-2023-25020/): WordPress Arigato Autoresponder and Newsletter Plugin <= 2.7.1.1 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2023-25061](https://insights.sbomify.com/CVE-2023-25061/): WordPress Arigato Autoresponder and Newsletter Plugin <= 2.7.1.1 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2023-25031](https://insights.sbomify.com/CVE-2023-25031/): WordPress Arigato Autoresponder and Newsletter Plugin <= 2.7.1 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)
- [CVE-2023-0543](https://insights.sbomify.com/CVE-2023-0543/): Arigato Autoresponder and Newsletter < 2.1.7.2 - Admin+ Stored XSS (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1002000 and fix it if it is affected.

What it is: CVE-2018-1002000 is a high-severity SQL injection vulnerability in Kiboko Labs https://calendarscripts.info/ Arigato Autoresponder and Newsletter, published on 3 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1002000 in the wild and no public exploit code.

Affected product: Kiboko Labs https://calendarscripts.info/ Arigato Autoresponder and Newsletter. 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-2018-1002000/ (Markdown: https://insights.sbomify.com/CVE-2018-1002000/index.md)
```

## Sources

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

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