Reflected XSS in We're Open! Opening Hours Plugin

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Noah Hearle We’re Open! opening-hours allows Reflected XSS.This issue affects We’re Open!: from n/a through 2.6.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

This vulnerability is a Reflected Cross-Site Scripting (XSS) flaw in the We're Open! WordPress plugin (versions through 2.6) that allows attackers to inject malicious scripts into web pages viewed by users. Reflected XSS vulnerabilities occur when user input is improperly sanitized and directly rendered in HTTP responses, enabling attackers to execute arbitrary JavaScript in victims' browsers. This matters because attackers can steal session cookies, perform actions on behalf of users, redirect to phishing sites, or harvest sensitive information from business websites that display operating hours. Any organization using the We're Open! plugin to display opening hours is affected, particularly small businesses and service providers who rely on WordPress for their web presence.

Casky's 323 mapped security skills leverage Claude's extended reasoning to detect the attack patterns underlying MITRE ATT&CK techniques TA0001 (Reconnaissance) and TA0043 (Reconnaissance via reverse proxy/scanning). When analyzing this CVE, practitioners would see Casky identify input vectors where opening hours data flows without proper HTML entity encoding or Content Security Policy enforcement—classic indicators of CWE-79. The platform's skills would surface specific detection patterns: monitoring for script tags in URL parameters, analyzing DOM manipulation patterns, and flagging unsafe JavaScript execution contexts. Practitioners using Casky would receive findings highlighting where user-controllable data enters the page generation pipeline without neutralization, along with recommended mitigations such as output encoding, input validation, and CSP headers—enabling teams to remediate before attackers exploit this vector against their web applications.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-112869.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-112869

Casky has 323 skills that investigate the attack patterns behind CVE-2026-112869. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn