Semantic MediaWiki versions from 2.5.0 up to but not including 7.3.1 have an improper authorization vulnerability. This flaw allows ordinary editors to add an 'Is edit protected' annotation, which causes indefinite edit and move restrictions to be applied without verifying the author's rights. As a result, other editors and administrators can be locked out of editing or moving pages permanently.
A Cross-Site Request Forgery (CSRF) vulnerability exists in the category management functionality of the Phoca Download Joomla extension versions 3.1.0 through 6.1.5. This vulnerability could allow an attacker to perform unauthorized actions on behalf of an authenticated user. The issue is classified as medium severity with a CVSS score of 5.3.
CVE-2026-107590 is an out-of-bounds write vulnerability in the Qt QTextCodec iconv-based encoding within the Qt 5 Compatibility APIs module. Under certain conditions, encoding text with QTextCodec may write outside an internal buffer, potentially causing application crashes and affecting data integrity. The vulnerability affects Qt versions from 4.5.0 up to and including 6.8.8, and from 6.9.0 up to and including 6.11.2. The CVSS 4.0 base score is 1.9, indicating low severity. No public exploits or patches are currently documented.
CVE-2026-100164 is an observable response discrepancy vulnerability in Rolantis Information Technologies Tourism Industry and Trade Co. Ltd.'s Agentis product. This flaw allows attackers to perform account footprinting by observing differences in system responses. The vulnerability affects Agentis versions prior to 4.8. A fix is available in version 4.8. The CVSS v3.1 base score is 7.5, indicating high severity, with network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact but no integrity or availability impact.
CVE-2026-13162 is an OS command injection vulnerability in Hitachi Energy's CoreTec 5 product. It affects the configuration daemon's time synchronization handler, which sets the system time-zone. Authenticated users with certain roles can exploit this flaw by supplying crafted input that is concatenated into shell commands without sanitization, allowing arbitrary system command execution with full device control. The vulnerability affects versions from 3.0.0 through 5.0.0 inclusive. The CVSS 4.0 score is 7.7, indicating high severity.
@fastify/express versions 4.0.5 through 4.0.8 contain a vulnerability where, if Fastify is configured with the non-default ignoreDuplicateSlashes option, path-scoped Express middleware may be bypassed. This occurs because Fastify's router normalizes duplicate slashes differently than Express when handling absolute-form request targets, allowing requests to reach scoped routes without passing through authentication or authorization middleware. The issue is fixed in version 4.0.9.
REDAXO core versions before 5.21.0 have a reflected cross-site scripting (XSS) vulnerability in the backend packages API. The flaw arises because a function parameter is concatenated into an error message without proper HTML escaping. An attacker can exploit this by tricking an authenticated backend user into clicking a crafted link containing a valid CSRF token, leading to JavaScript execution that can perform same-origin actions or read DOM data. This vulnerability is fixed in version 5.21.0.
REDAXO from 5.18.0 before 5.21.4 contains a stored cross-site scripting vulnerability because rex_media_service moves uploaded SVG files into the public media folder before sanitizing them. Authenticated users with mediapool upload rights can race the sanitizer or exhaust memory limits to leave script-laden SVGs publicly served, executing scripts in victims' backend sessions.
REDAXO core versions before 5.21.5 have a missing authorization vulnerability in the rex_api_package API function. This flaw allows non-admin backend users who possess a valid CSRF token to manage packages, including uninstalling system addons, deactivating, installing, activating packages, and deleting non-system packages. The vulnerability is fixed in version 5.21.5.
SemanticMediaWiki versions from 2.5.0 up to but not including 7.3.1 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows users with page-edit rights to inject malicious scripts via Code-typed property values. The vulnerability arises because the CodeStringValueFormatter renders annotated JSON values with embedded HTML markup unescaped on the Special:Browse page, enabling execution of JavaScript in the browsers of users viewing the page. The issue is fixed in version 7.3.1.
Semantic MediaWiki from 2.5.0 before 7.3.1 contains a stored cross-site scripting vulnerability that allows users with page-edit rights to inject scripts via External identifier property values. Attackers can annotate markup payloads that ExternalIdentifierValue renders unescaped on Special:Browse, executing JavaScript in viewers' sessions, including administrators.
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 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.