# CVE-2026-89305: Paymendo Bank Transfer <= 1.1 - Subscriber+ SQLi via 'orderBy' Parameter

> Authenticated users can execute SQL injection attacks via the orderBy parameter in the Paymendo Bank Transfer WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-cc47-x7cq-5www

## What is CVE-2026-89305?

CVE-2026-89305 is a medium-severity SQL injection vulnerability in Unknown paymendo, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The paymendo  WordPress plugin through 1.1 does not properly sanitize and escape a parameter before using it in a SQL query, allowing any authenticated user to perform SQL injection attacks.

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

## Which versions are affected by CVE-2026-89305?


## How do I fix CVE-2026-89305?

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

## Is CVE-2026-89305 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89305 and fix it if it is affected.

What it is: CVE-2026-89305 is a medium-severity SQL injection vulnerability in Unknown paymendo, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89305 in the wild and no public exploit code.

Affected product: Unknown paymendo. 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-2026-89305/ (Markdown: https://insights.sbomify.com/CVE-2026-89305/index.md)
```

## Sources

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

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