Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-100382 – Unauthenticated Remote Code Execution – MediaWiki ExternalData Extension (all vers

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-100382 is a critical OS command injection vulnerability in the ExternalData extension for MediaWiki, allowing unauthenticated, unauthenticated attackers to execute arbitrary system commands on the underlying server. The flaw is exploitable directly through wikitext or the Lua/Scribunto API and requires no authentication or user interaction, making it a full remote code execution (RCE) vector. The vulnerability has been assigned a maximum CVSS score of 10.0 and affects all versions of the extension prior to 3.7.

Technical details

  • Root cause: ExternalData’s EDConnectorExe connector, which is used by the #get_program_data parser function and the mw.ext.externalData.getProgramData() Lua function, passes attacker-controlled parameter values into a shell command execution call without adequate sanitization (CWE-78: Improper Neutralization of Special Elements used in an OS Command).
  • Trigger conditions:
    • Via wikitext, any user able to edit a page containing the parser function can inject shell commands, e.g. {{#get_program_data:program=a|Command=touch /tmp/externaldata.txt}}.
    • Via Lua (when Scribunto is enabled), attackers can craft parameter names containing whitespace to bypass existing input validation logic and reach the same vulnerable code path.
  • Attack vector: Network — no authentication, privileges, or user interaction are required to exploit the flaw where wiki editing is exposed (e.g., open or lightly-restricted wikis).
  • Impact: Full compromise of confidentiality, integrity, and availability of the host running the wiki, since arbitrary OS commands can be executed with the privileges of the web server/PHP process.

Affected software

  • MediaWiki ExternalData Extension — all versions prior to 3.7

Severity

  • CVSS Score: 10.0 (Critical)
  • CVSS v4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Mitigation and recommended actions

  • Immediate: Upgrade the ExternalData extension to version 3.7 or later, which trims/normalizes Lua parameter names to close the whitespace-based bypass and adds configuration support to disable individual connectors/parsers.
  • If immediate patching is not possible:
    • Disable the EDConnectorExe (program/executable) connector via ExternalData’s connector configuration, since this is the specific connector abused by the exploit.
    • Restrict page-editing and Lua/Scribunto module-editing permissions to trusted users only, reducing the pool of accounts that can inject the malicious parser function or Lua call.
    • Where feasible, disable or remove the ExternalData extension entirely until the upgrade can be applied, particularly on wikis open to anonymous or untrusted editors.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge