# CVE-2023-27610: WordPress Transbank Webpay REST Plugin <= 1.6.6 is vulnerable to SQL Injection

> Authenticated administrators can exploit SQL injection in the Transbank Webpay REST plugin to read or modify database contents.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-c8x6-66mv-5gv8

## What is CVE-2023-27610?

CVE-2023-27610 is a medium-severity SQL injection vulnerability in TransbankDevelopers Transbank Webpay REST, published on 16 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Auth. (admin+) SQL Injection (SQLi) vulnerability in TransbankDevelopers Transbank Webpay REST plugin <= 1.6.6 versions.

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

## Which versions are affected by CVE-2023-27610?

It affects 1 product.


Products: Transbank Transbank Webpay Rest.

## How do I fix CVE-2023-27610?

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

## Is CVE-2023-27610 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27610 and fix it if it is affected.

What it is: CVE-2023-27610 is a medium-severity SQL injection vulnerability in TransbankDevelopers Transbank Webpay REST, published on 16 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-27610 in the wild and no public exploit code.

Affected product: TransbankDevelopers Transbank Webpay REST. 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-2023-27610/ (Markdown: https://insights.sbomify.com/CVE-2023-27610/index.md)
```

## Sources

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

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