CVE-2026-125815 · Package
NO FIX YET · SEE WHAT TO DO
The We're Open! opening-hours plugin for WordPress fails to neutralize script-related HTML tags, so input can inject code into web pages. An attacker who can get a crafted value into the plugin's output can run script in a visitor's browser.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the We're Open! opening-hours WordPress plugin at version 2.8 or earlier are in the affected range. The sources do not say which page or input path is exploitable or whether an account is needed, so unknown what the exposure looks like beyond the version range.
Not affected if plugin-not-installed
Who cares we're open!, wordpress
We're Open! opening-hours plugin is installed on the WordPress site (Plugins list in wp-admin)2.8; anything at or below 2.8 is in the affected rangeImproper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in Noah Hearle We’re Open! opening-hours allows Code Injection.This issue affects We’re Open!: from n/a through 2.8.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.