Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesWe’re Open!

We’re Open! vulnerabilities

We’re Open! has 4 known vulnerabilities in this database. The most recent published record is dated 13 Nov 2026.

Known vulnerabilities
4
Active installs
5,000+
Latest version
2.8
Last updated
28 Oct 2026
Most recent
13 Nov 2026

No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
Cross-site scripting (XSS)
CVE-2026-125815
Medium 5.3Up to 2.8No fixed version yet9 d ago
Cross-site scripting (XSS)
CVE-2026-112869
High 7.1Up to 2.6Fixed in a later version (latest 2.8)24 Oct 2026
Cross-site scripting (XSS)
CVE-2022-4752
Medium 5.4Up to 2.3.0Fixed in a later version (latest 2.8)21 Feb 2023
Cross-site scripting (XSS)
CVE-2022-3139
Medium 4.8Before 1.42Fixed in 1.4217 Oct 2022
Read the published descriptions
CVE-2026-125815, 13 Nov 2026
Improper 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. CVE record
CVE-2026-112869, 24 Oct 2026
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. CVE record
CVE-2022-4752, 21 Feb 2023
The Opening Hours WordPress plugin through 2.3.0 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks CVE record
CVE-2022-3139, 17 Oct 2022
The We’re Open! WordPress plugin before 1.42 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record

What to do if you run We’re Open!

If you run We’re Open!, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.

If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.

Email me about new We’re Open! vulnerabilities

Free. We email you when a new vulnerability is published for We’re Open!, usually within minutes. Confirm by email; unsubscribe any time.

Focus on your business. We’ll take care of your website.

From everyday updates to ongoing care, we keep your website working.

Get website support