SemanticMediaWiki versions from 5.0.0 up to but not including 7.3.1 contain a stored cross-site scripting (XSS) vulnerability in the ext.smw.tooltip.tippy.js component. This flaw allows editors to inject malicious JavaScript via specially crafted data-* attributes in .smw-highlighter spans, which execute when users hover over them. The vulnerability is fixed in version 7.3.1.
Semantic MediaWiki versions from 3.1.0 up to but not including 7.3.1 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows authenticated users with the smw-schemaedit permission to inject malicious HTML through schema descriptions. The injected HTML is passed unescaped to Html::rawElement() in HtmlBuilder, which can alter pages and affect users who view the compromised schema. The vulnerability is fixed in version 7.3.1.
Semantic MediaWiki from 4.2.0 before 7.3.1 contains a stored cross-site scripting vulnerability that allows authenticated profile or schema editors to inject HTML through FacetedSearch exploration-link labels. Attackers can store markup in the label, which ExploreListBuilder::buildHTML() passes unescaped to Html::rawElement(), altering the Special:FacetedSearch page and potentially running scripts in viewers' browsers.
Semantic MediaWiki versions from 3.0.0 up to but not including 7.3.1 contain a cross-site scripting (XSS) vulnerability. This flaw allows attackers to inject malicious markup into semantic property values that are rendered unescaped in autocomplete suggestions. When a user opens the property-value autocomplete with an empty query, the vulnerable jquery.autocomplete.js script inserts raw API values directly into HTML, potentially executing arbitrary scripts. The vulnerability is fixed in version 7.3.1.
Semantic MediaWiki versions from 3.0.0 up to but not including 7.3.1 contain a cross-site request forgery (CSRF) vulnerability in the Special:SMWAdmin page. This flaw allows an attacker to trick an authenticated smw-admin user into performing unintended actions such as schema setup, entity disposal, or job execution, potentially leading to semantic data loss and resource exhaustion. The vulnerability is fixed in version 7.3.1.
Semantic MediaWiki versions 7.3.0 before 7.3.1 have a missing authorization vulnerability in the smwtask update task. This flaw allows users with edit rights to force semantic updates on arbitrary pages, including restricted ones, by supplying a crafted serialized subject parameter. The forced reparsing can lead to semantic-store writes and resource-intensive dependency processing.
Semantic MediaWiki from 2.5.0 before 7.3.1 contains an uncontrolled resource consumption vulnerability that allows anonymous attackers to force quadratic computation by supplying a zero limit to Special:PropertyLabelSimilarity. Attackers can send repeated requests with limit=0 to bypass the SQL LIMIT and trigger pairwise similar_text() comparisons, exhausting PHP CPU, memory, and database connections.
Semantic MediaWiki versions from 2.5.0 up to but not including 7.3.1 contain a vulnerability that allows low-privilege editors to cause uncontrolled resource consumption. By supplying a large limit parameter to the #set_recurring_event parser function without specifying an end date, attackers can generate a massive number of date subobjects. This leads to exhaustion of CPU, memory, and database resources. The issue is fixed in version 7.3.1.
Semantic MediaWiki versions from 2.5.0 up to but not including 7.3.1 have an authorization vulnerability that allows ordinary editors to permanently protect pages by adding an 'Is edit protected' annotation. This occurs when the $smwgEditProtectionRight setting is enabled, causing the EditProtectionUpdater to apply indefinite edit and move restrictions without verifying the author's permissions, effectively locking out other editors and administrators.
SemanticMediaWiki versions from 3.0.0 up to but not including 7.3.1 contain a reflected cross-site scripting (XSS) vulnerability in the Special:Ask feature. This flaw arises because certain separator parameters are output without proper HTML escaping in various result printers. An unauthenticated attacker can craft malicious links that execute JavaScript in the context of the wiki, potentially stealing session cookies or CSRF tokens. The vulnerability is fixed in version 7.3.1.
SemanticMediaWiki from 3.1.0 before 7.3.1 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the unescaped default parameter in JsonResultPrinter. Attackers can lure victims to a crafted Special:Ask link with a zero-result query and request_type=special_page, executing JavaScript in the wiki origin to steal sessions or CSRF tokens.
Semantic MediaWiki versions 7.3.0 before 7.3.1 have a missing authorization vulnerability in the smwtask API module. This flaw allows unauthenticated attackers to run queued jobs and force store updates. Attackers can exploit the public anonymous CSRF token with run-joblist to execute arbitrary job types repeatedly or invoke updates on sysop-protected pages, potentially leaking page titles and exhausting system resources. The vulnerability is fixed in version 7.3.1.
Semantic MediaWiki versions from 3.0.0 up to but not including 7.3.1 contain an algorithmic complexity vulnerability in the TermParser::normalize_compact_form() function. This flaw allows unauthenticated attackers to cause quadratic CPU consumption by submitting long search terms with many distinct in:(...) or has:(...) expressions to Special:Search when the extended search engine is enabled. The vulnerability can exhaust PHP search workers, impacting service availability. A fix is available in version 7.3.1.
Semantic MediaWiki versions 3.0.0 through 7.3.0 contain an uncontrolled recursion vulnerability in the LegacyParser::getSubqueryDescription() function. This flaw allows unauthenticated attackers to submit deeply nested query elements via the action=ask API, causing excessive CPU and memory consumption and tying up server request workers. The vulnerability is fixed in version 7.3.1.
CVE-2026-117530 is a vulnerability in JetBrains Junie CLI versions before 26.8.17 where incomplete validation of allowlisted commands allowed command execution. This flaw was addressed and fixed in version 26.8.17.
CVE-2026-111548 is a stack-based buffer overflow vulnerability in the web management interface of Moxa NPort W2150A-W4 and W2250A-W4 series wireless device servers. An authenticated remote attacker with low privileges can exploit insufficient bounds checking of user input to cause the web management service to become unresponsive. Recovery requires power cycling the affected device, though other device functions continue operating.
CVE-2026-82117 is a critical authentication bypass vulnerability in Hitachi HiRDB Server Version 10 and certain versions of Version 9. The flaw allows an attacker to bypass authentication by spoofing, potentially leading to full compromise of confidentiality, integrity, and availability. The vulnerability affects HiRDB Server Version 10 from 10-00 up to but not including 10-12-01, and multiple Version 9 releases. A fix is available in version 10-12-01.
CVE-2026-82116 is a critical vulnerability in Hitachi HiRDB Server Version 10 and certain versions of Version 9 that involves missing authentication for a critical function. This flaw allows unauthenticated remote attackers to potentially execute unauthorized actions with high impact on confidentiality, integrity, and availability. The vulnerability affects multiple versions prior to 10-12-01 and has been assigned a CVSS score of 9.8, indicating critical severity. A fix is available in version 10-12-01.
CVE-2026-82118 is a critical stack-based buffer overflow vulnerability affecting Hitachi HiRDB Server versions 9 and 10. The flaw exists in versions from 10-00 up to but not including 10-12-01, and in various 9.x versions up to 09-66-22. This vulnerability allows an attacker to execute arbitrary code or cause a denial of service due to memory corruption.
CVE-2026-82120 is a critical heap-based buffer overflow vulnerability affecting Hitachi HiRDB Server versions 9 and 10 within specified version ranges. The flaw allows an attacker to potentially execute arbitrary code or cause denial of service due to memory corruption. A fix is available in HiRDB Server version 10-12-01.