VYPR
Moderate severityNVD Advisory· Published Jan 12, 2018· Updated Aug 5, 2024

CVE-2018-5367

CVE-2018-5367

Description

The WPGlobus plugin 1.9.6 for WordPress is vulnerable to stored XSS via the wpglobus_option[post_type][post] parameter in wp-admin/options.php, due to insufficient input sanitization.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

The WPGlobus plugin 1.9.6 for WordPress is vulnerable to stored XSS via the wpglobus_option[post_type][post] parameter in wp-admin/options.php, due to insufficient input sanitization.

Vulnerability

The WPGlobus plugin version 1.9.6 for WordPress contains a stored cross-site scripting (XSS) vulnerability in the wpglobus_option[post_type][post] parameter, which is processed by wp-admin/options.php. The plugin fails to properly sanitize or escape user-supplied input before storing it in the database, allowing arbitrary HTML and JavaScript to be injected. [1]

Exploitation

An attacker can exploit this vulnerability by sending a crafted HTTP POST request to wp-admin/options.php with the malicious payload in the wpglobus_option[post_type][post] parameter. The attack requires a user with administrator privileges to submit the form (e.g., via the WPGlobus settings page). The lack of a CSRF nonce in the settings form [1] means the attack can be chained with cross-site request forgery: an attacker can trick an authenticated admin into unknowingly submitting the malicious payload via a crafted HTML page, achieving stored XSS on the admin panel. [1]

Impact

Successful exploitation results in stored XSS within the WordPress admin interface. An attacker can execute arbitrary JavaScript in the context of the logged-in administrator's session. This could lead to privilege escalation, sensitive data theft, or full site compromise by injecting malicious scripts that run when the targeted admin or other users view the affected page. [1]

Mitigation

As of the publication date (2018-01-12), no official patch or fixed version has been released by the vendor. The recommended mitigation is to disable the WPGlobus plugin until an update is available. Alternatively, implement a web application firewall (WAF) rule to block malicious input patterns targeting the vulnerable parameter. [1]

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
wpglobus/wpglobusPackagist
< 1.9.71.9.7

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

4

News mentions

0

No linked articles in our index yet.