Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-58289 Overview
CVE-2024-58289 is a stored cross-site scripting (XSS) vulnerability in Microweber 2.0.15, an open-source content management system. The flaw resides in user profile fields, where the application fails to sanitize input submitted to the first name field. Authenticated attackers can inject arbitrary JavaScript that executes in the browser of any user who views the affected profile. Successful exploitation enables session cookie theft, account takeover, and client-side code execution within the application context. The weakness is tracked under CWE-79: Improper Neutralization of Input During Web Page Generation.
Critical Impact
Authenticated attackers can execute arbitrary JavaScript in other users' browsers, enabling session hijacking and credential theft through the Microweber user profile system.
Affected Products
- Microweber CMS version 2.0.15
- Deployments exposing user profile viewing to authenticated users
- Self-hosted and cloud-hosted Microweber instances running the affected release
Discovery Timeline
- 2025-12-11 - CVE-2024-58289 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-58289
Vulnerability Analysis
Microweber 2.0.15 stores user-supplied profile data without applying output encoding when the first name field is rendered to other users. An authenticated attacker who places a script payload into the first name field causes the payload to persist in the backend data store. The malicious markup executes when another authenticated user, including administrators, views the attacker-controlled profile. Because the script runs in the context of the Microweber origin, it can read session cookies, invoke authenticated API calls, modify page content, and pivot to administrative functionality.
Root Cause
The root cause is missing input validation and output encoding on the first name profile field. User-supplied values are concatenated into HTML templates without HTML entity encoding or allowlist filtering, which permits raw <script> tags and HTML event handlers to render as executable markup.
Attack Vector
Exploitation requires authenticated access with permission to edit a user profile. The attacker submits a crafted payload through the profile edit form, then waits for or lures a victim to view the profile. No additional user interaction beyond viewing the profile is required for execution. Public references include Exploit-DB #52058 and the VulnCheck Advisory on Microweber XSS.
No verified proof-of-concept code is reproduced here. The vulnerability mechanism involves storing JavaScript inside a profile field and triggering it on the server-rendered profile page. Refer to the linked advisories for payload specifics.
Detection Methods for CVE-2024-58289
Indicators of Compromise
- Profile records containing HTML tags such as <script>, <img onerror=>, or <svg onload=> in the first name field.
- Outbound HTTP requests from user browsers to attacker-controlled domains following profile page views.
- Unexpected session cookie exfiltration patterns or spikes in authenticated API calls originating from administrator sessions.
Detection Strategies
- Query the Microweber user database for profile fields containing angle brackets, javascript: schemes, or event handler attributes.
- Review web server access logs for POST requests to profile update endpoints submitting payloads with HTML control characters.
- Correlate browser-side errors, Content Security Policy violation reports, and anomalous JavaScript execution timings on profile view routes.
Monitoring Recommendations
- Enable and monitor Content Security Policy reporting endpoints for violations tied to inline script execution on profile pages.
- Alert on administrative session activity immediately following views of recently modified user profiles.
- Audit changes to user profile records at the database layer and retain diffs for forensic review.
How to Mitigate CVE-2024-58289
Immediate Actions Required
- Upgrade Microweber to the latest release above 2.0.15 that remediates the profile field sanitization gap.
- Audit existing user profiles for stored HTML or JavaScript payloads and purge any identified malicious content.
- Invalidate active sessions and force password resets for administrators who may have viewed untrusted profiles.
Patch Information
Monitor the GitHub Repository for Microweber and the Microweber Official Website for the fixed release. Apply the patched version in a staging environment, verify that profile fields enforce HTML encoding on output, and promote to production once validated.
Workarounds
- Restrict user registration and profile editing to trusted accounts until the patch is applied.
- Deploy a web application firewall rule that blocks angle brackets and event handler attributes in profile field submissions.
- Implement a strict Content Security Policy that disallows inline scripts on authenticated application routes.
- Add server-side input validation that rejects HTML markup in name fields as a compensating control.
# Example Content-Security-Policy header to limit inline script execution
Content-Security-Policy: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; report-uri /csp-report
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

