CVE-2026-3995

{"id": "CVE-2026-3995", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "security@wordfence.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 4.4, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "LOW"}, "impactScore": 2.7, "exploitabilityScore": 1.3}]}, "published": "2026-04-16T07:16:30.503", "references": [{"url": "https://plugins.trac.wordpress.org/browser/open-brain/tags/0.5.0/index.php#L128", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/open-brain/tags/0.5.0/index.php#L252", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/open-brain/tags/0.5.0/index.php#L253", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/open-brain/tags/0.5.0/index.php#L272", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/open-brain/trunk/index.php#L128", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/open-brain/trunk/index.php#L252", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/open-brain/trunk/index.php#L253", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/open-brain/trunk/index.php#L272", "source": "security@wordfence.com"}, {"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/3fe3fa95-cc1d-469b-8a97-37987b9ae362?source=cve", "source": "security@wordfence.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Primary", "source": "security@wordfence.com", "description": [{"lang": "en", "value": "CWE-79"}]}], "descriptions": [{"lang": "en", "value": "The OPEN-BRAIN plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'API Key' settings field in all versions up to, and including, 0.5.0. This is due to insufficient input sanitization and output escaping. The plugin uses sanitize_text_field() which strips HTML tags but does not encode double quotes or other HTML-special characters needed for safe attribute context output. The API key value is saved via update_option() and later output into an HTML input element's value attribute without esc_attr() escaping. This makes it possible for authenticated attackers, with Administrator-level access, to inject arbitrary web scripts via attribute breakout payloads (e.g., double quotes followed by event handlers) that execute whenever a user accesses the plugin settings page."}], "lastModified": "2026-04-22T20:22:50.570", "sourceIdentifier": "security@wordfence.com"}