Skip to main content

We're Open! Plugin EUVDEUVD-2026-109248

| CVE-2026-112869 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-24 Patchstack GHSA-3fr8-4p6j-5pqc
7.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft URL with XSS payload in reflected parameter
  2. Exploit
    Lure logged-in user to click link
  3. Execution
    Payload reflects into generated page and executes
  4. Impact
    Run script in victim's browser context to hijack session

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to get a victim who has access to the affected 'We're Open!' plugin pages to open an attacker-crafted request/URL (UI:R) - the reflected payload is not stored, so there is no persistence and no server-side authentication is needed by the attacker (PR:N). The specific vulnerable parameter or input field is not described in the available sources. Key limiting factors: the attack fails without user interaction, affects only sites running the plugin at versions up to 2.6, and yields execution only in the victim's browser session rather than direct server compromise; impact is amplified if the lured victim is a privileged/administrator user.

Impact

This is a reflected cross-site scripting flaw (CWE-79) in the WordPress plugin 'We're Open!' (opening-hours) carrying a CVSS 3.1 base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L). The vector signals network-reachable, low-complexity exploitation requiring no attacker privileges but DOES require user interaction (UI:R) - the victim must be lured into triggering the reflected payload, which is the single largest brake on real-world risk. The scope change (S:C) and low C/I/A impacts are consistent with script execution in the victim's browser context rather than server compromise. No EPSS score is provided in the input, there is no CISA KEV listing, and no verified exploit code is supplied, so there is no public exploit identified at time of analysis. The only intelligence source is a Patchstack database advisory, and the vuln.today decision label is 'this_week' (not act_now/emergency), so this is a genuine but moderate, interaction-dependent priority rather than a mass-exploitation emergency. Note a mild tension to verify with the vendor: reflected XSS normally yields only low confidentiality/integrity impact, yet the vector claims A:L (availability) impact, which is atypical for reflected XSS and appears to reflect Patchstack's standard scoring template rather than a demonstrated denial-of-service.

Exploit ScenarioDerived

An attacker crafts a URL for a site running the 'We're Open!' plugin that embeds a malicious script in a reflected parameter, then delivers it to a logged-in user (e.g. an administrator) via phishing or a planted link. When the victim opens the link, the unsanitized input is reflected into the generated page and executes in their browser, letting the attacker run script in the site's context - for example to hijack the session or perform actions as the victim. No public exploit was identified at time of analysis, and successful attack depends on the victim actually clicking the crafted link (UI:R).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 24, 2026

Reflected cross-site scripting in the WordPress plugin 'We're Open!' (opening-hours) through version 2.6 allows remote attackers to execute script in a victim's browser session when the victim opens a crafted URL, with no authentication required on the attacker's side (CVSS 3.1: 7.1, AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L). The payload is not stored, so exploitation depends on luring a user who can reach the affected plugin pages - impact is greater if that user is an administrator. No public exploit code or CISA KEV entry was identified at the time of analysis, and the specific vulnerable parameter is not described in the available sources.

RemediationAI

The provided intelligence does not list a fixed release version; the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/opening-hours/vulnerability/wordpress-we-re-open-plugin-2-6-cross-site-scripting-xss-vulnerability is the reference to check for an updated plugin build. If a patched version is published, updating 'We're Open!' past 2.6 removes the affected code path; if the plugin is not required, deactivating and deleting it eliminates the reflected XSS surface, with the trade-off that opening-hours display functionality is lost. Because the issue is reflected and requires the victim to open a crafted request (UI:R), the available data does not identify a server-side configuration toggle that blocks the payload while preserving plugin functionality.

Affected VersionsENISA

We’re Open! 0 ≤2.6

Affected Packages

euvd we_re_open no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically reflected XSS in the WordPress plugin 'We're Open!' (slug opening-hours) by Noah Hearle. Reflected XSS occurs when a request parameter is echoed back into generated HTML without adequate encoding, so a crafted link causes the browser to execute attacker-supplied script in the origin of the WordPress site. The CPE cpe:2.3:a:noah_hearle:we’re_open!:*:*:*:*:*:*:*: identifies the plugin as the affected component, and the CVSS scope-changed metric (S:C) reflects that the script can affect resources beyond the vulnerable component's security scope, such as actions available to the victim's WordPress session. The advisory does not name the vulnerable parameter or exact code path, and there is no evidence of persistence or server-side compromise; impact is confined to the victim's browser and the privileges of that session.

Know when Wordpress Plugin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 7.1 HIGH

Reflected XSS is network-reachable and low-complexity with no attacker auth (PR:N) but needs the victim to click (UI:R); script runs in the browser across a trust boundary (S:C) with limited C/I impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A high-severity reflected cross-site scripting (XSS) vulnerability in the WordPress plugin 'We're Open!' (opening-hours) versions up to 2.6 could allow an attacker to execute malicious scripts in a victim's browser, potentially leading to session hijacking or actions performed on behalf of the victim. While no active exploitation has been observed, the risk is elevated because the plugin is widely used and an administrator visiting a crafted link could compromise the entire site. Leadership should prioritize remediation to protect site integrity and user trust.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable the plugin until a patch is available; deploy WAF rules to filter malicious input; restrict administrative access and enforce least privilege; conduct user awareness training on phishing and suspicious links.

Threat Intelligence Overview

EPSS Score
0.3%
Top 84% exploitable
Prevalence
Low
niche WordPress opening-hours plugin, limited installation base
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy