← back to feed
CVE-2026-111110

CVE-2026-111110

validatedZero produced an exploit or a check.

GHSA-xm8j-r35j-8pr2 ↗EUVD-2026-103275 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
stiofansisland Payment forms, Buy now buttons, and Invoicing System | GetPaid <= 2.8.61
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-2161Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss7.2cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
+3.2dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dcheck available+3.2dagent stopped
0
+1d
+2d

description

GetPaid for WordPress versions through 2.8.61 are affected by a stored cross-site scripting flaw. An unauthenticated attacker may cause script to run in an administrator's browser when the administrator views payment-form details for an affected invoice; public availability of the required request token removes the need for prior access.

mitigation

Disable the GetPaid plugin or restrict public access to its payment-form and invoice functionality until a vendor-fixed release is available. Limit administrator access to untrusted invoice records and review affected invoices for injected content.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.28%19th percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-17 07:51Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-17 07:51Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-111110
  2. 2026-10-20 11:27Z

this entry in the feed

GET /api/v1/feed/CVE-2026-111110

{
  "etk_id": "ETK-2026-2161",
  "cve_id": "CVE-2026-111110",
  "display_id": "CVE-2026-111110",
  "ghsa_id": "GHSA-xm8j-r35j-8pr2",
  "euvd_id": "EUVD-2026-103275",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in GetPaid for WordPress",
  "summary": "GetPaid for WordPress versions through 2.8.61 are affected by a stored cross-site scripting flaw. An unauthenticated attacker may cause script to run in an administrator's browser when the administrator views payment-form details for an affected invoice; public availability of the required request token removes the need for prior access.",
  "mitigation": "Disable the GetPaid plugin or restrict public access to its payment-form and invoice functionality until a vendor-fixed release is available. Limit administrator access to untrusted invoice records and review affected invoices for injected content.",
  "vendor": "stiofansisland",
  "product": "Payment forms, Buy now buttons, and Invoicing System | GetPaid",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.8.61"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Payment forms, Buy now buttons, and Invoicing System | GetPaid",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
  "epss_score": 0.0028,
  "epss_percentile": 0.1904,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.014596516666666667,
  "t0_at": "2026-10-17T07:51:24.536000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-20T11:27:30.590784+00:00",
      "days": 3.1500700785185183,
      "is_lower_bound": false,
      "measured_at": "2026-10-17T07:51:24.536000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-17T07:51:24.536000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-17T07:51:24.536000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111110"
    }
  }
}

published 2026-10-20 11:27Z
last change 2026-10-21 09:11Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.