EUVD-2026-23974
GHSA-4qgv-929g-c62m
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
The Image Source Control Lite - Show Image Credits and Captions plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Image Source' attachment field in all versions up to, and including, 3.9.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
AnalysisAI
Stored XSS in Image Source Control Lite WordPress plugin versions up to 3.9.1 allows authenticated attackers with Author-level permissions or higher to inject malicious scripts via the 'Image Source' attachment field, executing arbitrary JavaScript in the browsers of any user viewing affected pages. The vulnerability stems from insufficient input sanitization and output escaping in the attachment metadata handler. No public exploit code or active exploitation has been confirmed at the time of analysis, but the low attack complexity and network accessibility make this a practical risk for multi-author WordPress installations.
Technical ContextAI
Image Source Control Lite (CPE: cpe:2.3:a:webzunft:image_source_control_lite_-_show_image_credits_and_captions:*:*:*:*:*:*:*:*) is a WordPress plugin that extends attachment metadata fields to store image source and credit information. The vulnerability exists in the 'Image Source' field handler, which accepts user input from authenticated authors during media library management but fails to properly escape this data when rendering it in attachment metadata displays or frontend image credit sections. The affected code path involves the attachment field storage (post meta) and subsequent retrieval without HTML escaping, allowing stored JavaScript payloads to persist in the database and execute in any user's session that views the attachment or page containing the embedded image. This is a classic Stored XSS (CWE-79: Improper Neutralization of Input During Web Page Generation) where trust is granted to authenticated input without output context-aware escaping.
RemediationAI
Update Image Source Control Lite to a patched version released after 3.9.1. At the time of this analysis, the exact patched version number has not been independently confirmed from the provided references; users should check the WordPress.org plugin repository or Wordfence's vulnerability advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/db0222e2-5a50-43f4-8620-12b97c712dec?source=cve) for the latest available release. Until patching is possible, implement the following compensating controls: (1) Restrict Author-level and above capabilities to trusted users only; audit existing author accounts for compromised credentials. (2) Disable the 'Image Source' field feature within the plugin settings if the option exists, preventing the vulnerable input vector. (3) Use WordPress user role and capability management plugins (e.g., Members, Admin Columns) to enforce stricter editorial permissions, limiting who can edit attachment metadata. (4) Implement Web Application Firewall (WAF) rules to detect and block stored XSS payloads in POST/PUT requests to wp-admin media endpoints, filtering for HTML/JavaScript patterns in attachment meta fields. (5) Monitor the plugin's issue tracker and enable automatic updates for the plugin once a patched version is confirmed released. Trade-offs: restricting author access may impact editorial workflows; disabling the Image Source field removes the plugin's core functionality; WAF rules require careful tuning to avoid false positives on legitimate rich-text metadata.
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today