PatchSiren cyber security CVE debrief
CVE-2026-112869 Noah Hearle CVE debrief
A Cross-site Scripting (XSS) vulnerability exists in the We’re Open! plugin for WordPress, affecting versions from n/a through 2.6. This issue allows for Reflected XSS attacks. The vulnerability can lead to unauthorized actions or data exposure, emphasizing the need for verification of affected versions and implementation of compensating controls. Defenders should prioritize verifying exposure and implementing measures to prevent exploitation. Further verification is required to determine the full scope of affected versions and potential impact.
- Vendor
- Noah Hearle
- Product
- We’re Open!
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-24
- Original CVE updated
- 2026-10-24
- Advisory published
- 2026-10-24
- Advisory updated
- 2026-10-24
Who should care
Defenders responsible for WordPress deployments using the We’re Open! plugin should assess exposure and prioritize verification and mitigation efforts.
Why it matters
CVE-2026-112869 is a Cross-site Scripting (XSS) vulnerability in the We’re Open! plugin for WordPress. Defenders should prioritize verifying exposure, implementing compensating controls, and monitoring for potential attacks. The vulnerability affects versions from n/a through 2.6 and allows for Reflected XSS attacks.
- Potential for Reflected XSS attacks, which could lead to unauthorized actions or data exposure.
- Need for verification of affected versions and implementation of compensating controls.
- Potential impact on user interactions with the affected plugin.
Technical summary
The We’re Open! plugin for WordPress is vulnerable to Cross-site Scripting (XSS) attacks. The issue affects versions from n/a through 2.6 and allows for Reflected XSS. This vulnerability can be exploited through user interactions with the affected plugin, potentially leading to unauthorized actions or data exposure. Defenders should focus on verifying exposure, implementing compensating controls such as input validation and output encoding, and monitoring for potential attacks.
Defensive priority
Defenders should prioritize verifying exposure and implementing compensating controls to prevent exploitation.
Recommended defensive actions
- Verify exposure by checking if the We’re Open! plugin version is within the affected range (from n/a through 2.6).
- Implement compensating controls, such as input validation and output encoding, to prevent exploitation.
- Monitor for potential XSS attacks and update the plugin to a fixed version when available.
Evidence notes
The CVE record and NVD entry provide limited information about the vulnerability. Further verification is required to determine the full scope of affected versions and potential impact.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-112869 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-112869
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-112869 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-112869
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.