CVE-2024-11688

LaTeX2HTML <= 2.5.5 - Reflected Cross-Site Scripting

2024-12-20 20:38
vgo0

Strategic Overview

Status
Patched in 2.6.0
Affected Plugin
LaTeX2HTML
Affected Version
<= 2.5.5
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2024-11688
View all LaTeX2HTML vulnerabilities

At a glance

CVE-2024-11688 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the LaTeX2HTML WordPress plugin, affecting versions <= 2.5.5. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.6.0; sites on affected versions should update now. Disclosed December 2024, reported by vgo0.

Vulnerability Overview

The LaTeX2HTML plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'ver' or 'date' parameter in all versions up to, and including, 2.5.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

LaTeX2HTML <= 2.5.5 carries this weakness at ver, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For LaTeX2HTML the fix is 2.6.0: builds <= 2.5.5 are affected, anything from 2.6.0 onward is not.

Remediation

Update to version 2.6.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to LaTeX2HTML: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: LaTeX2HTML 2.6.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C