sales@hackhalt.com

Home / Threats / CVE-2026-119747

GetPaid - Security Vulnerability (CVE-2026-119747)

CVE-2026-119747

The GetPaid plugin for WordPress before 2.8.63 contains an incorrect authorization vulnerability where the check_post_permissions() method in includes/api/class-getpaid-rest-posts-controller.php maps REST operations to generic WordPress post capabilities instead of enforcing the plugin's manage_invoicing permission. Authenticated users with lower-privileged roles such as Editor or Author can exploit this flaw to list other users' invoices, mark pending invoices as paid without recording payment transactions, or create published items and new invoices through the REST API.

CVE-2026-119747

HIGH CVSS 7.1 Published 2026-11-04 Updated 2026-11-04
AI Risk Elevated (65/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band HIGH
CVSS Vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Affected Components 2
Reference Links 2
AI Risk Engine Elevated (65/100)
Exploitability Medium
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-11-04 CVE published and first recorded in the threat feed.
  2. 2026-11-04 Record updated with latest vulnerability metadata.
  3. 2026-11-12 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 17 hours ago

AI enriched 17 hours ago (2026-11-12 02:28 UTC)

Technical Summary

The GetPaid plugin for WordPress before 2.8.63 contains an incorrect authorization vulnerability where the check_post_permissions() method in includes/api/class-getpaid-rest-posts-controller.php maps REST operations to generic WordPress post capabilities instead of enforcing the plugin's manage_invoicing permission. Authenticated users with lower-privileged roles such as Editor or Author can exploit this flaw to list other users' invoices, mark pending invoices as paid without recording payment transactions, or create published items and new invoices through the REST API.

Potential Impact

Severity is HIGH (CVSS 7.1). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 65/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

GetPaid PLUGIN · getpaid Affected: < 2.8.63 Fixed in: 2.8.63
Invoicing PLUGIN · invoicing Affected: < 2.8.63 Fixed in: 2.8.63

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update GetPaid to 2.8.63 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs GetPaid, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs GetPaid. Versions below 2.8.63 are vulnerable; that release and later are not.

How do I fix it?

Update GetPaid to version 2.8.63 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Broken Access Control flaw. An attacker who exploits it can reach actions or data that should have been restricted to someone else.