# CVE-2026-119748: GetPaid WordPress Plugin < 2.8.63 Authorization Bypass via maybe_use_invoice


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-hr58-8ppj-xwvg

## What is CVE-2026-119748?

CVE-2026-119748 is a medium-severity vulnerability in AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid, published on 4 Nov 2026. 

### Official description

The GetPaid plugin for WordPress before 2.8.63 contains an authorization bypass vulnerability that allows unauthenticated attackers to access and manipulate another user's invoice by supplying its ID through the maybe_use_invoice parameter in process_invoice(), bypassing the ownership and key checks performed by is_authorized_to_pay(). Attackers can submit a known pending invoice ID via maybe_use_invoice to read checkout pricing details and initiate a checkout workflow, resulting in an unauthorized state change of the invoice to on-hold.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-119748 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119748 is a medium-severity vulnerability in AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119748 in the wild and no public exploit code.

Affected product: AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid. 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-119748/ (Markdown: https://insights.sbomify.com/CVE-2026-119748/index.md)
```

## Sources

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

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