← back to feed
CVE-2026-115811

CVE-2026-115811

validatedZero produced an exploit or a check.

EUVD-2026-118973 ↗

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.
wpchill Strong Testimonials <= 3.3.16
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-3803Zero'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
+38mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+38magent stopped
0
+10min
+20min
+30min
+40min

description

Strong Testimonials for WordPress through version 3.3.16 is affected by stored cross-site scripting in testimonial rating handling. An unauthenticated attacker may cause attacker-supplied script to run in a visitor's browser when an administrator previews a pending testimonial. Exploitation depends on an administrator opening the normal preview for the submitted testimonial.

mitigation

Update Strong Testimonials when a vendor-fixed release becomes available. Until then, restrict or disable untrusted testimonial submissions and do not preview pending testimonials from untrusted sources.

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.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-07 06:39Z
Δ 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-11-07 06:39Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-115811
  2. 2026-11-07 07:17Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3803",
  "cve_id": "CVE-2026-115811",
  "display_id": "CVE-2026-115811",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-118973",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in Strong Testimonials",
  "summary": "Strong Testimonials for WordPress through version 3.3.16 is affected by stored cross-site scripting in testimonial rating handling. An unauthenticated attacker may cause attacker-supplied script to run in a visitor's browser when an administrator previews a pending testimonial. Exploitation depends on an administrator opening the normal preview for the submitted testimonial.",
  "mitigation": "Update Strong Testimonials when a vendor-fixed release becomes available. Until then, restrict or disable untrusted testimonial submissions and do not preview pending testimonials from untrusted sources.",
  "vendor": "wpchill",
  "product": "Strong Testimonials",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.3.16"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Strong Testimonials",
      "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.27669261666666667,
  "t0_at": "2026-11-07T06:39:41.699000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-07T07:17:32.116362+00:00",
      "days": 0.026277978726851853,
      "is_lower_bound": false,
      "measured_at": "2026-11-07T06:39:41.699000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-07T06:39:41.699000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-07T06:39:41.699000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-115811"
    }
  }
}

published 2026-11-07 07:17Z
last change 2026-11-07 08:37Z

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.