CVE-2025-5488
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-06-26

Last updated on: 2025-07-11

Assigner: Wordfence

Description
The WP Masonry & Infinite Scroll plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wmis' shortcode in all versions up to, and including, 2.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-26
Last Modified
2025-07-11
Generated
2026-05-07
AI Q&A
2025-06-26
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
kaushik07 wp_masonry_\&_infinite_scroll to 2.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-5488 is a Stored Cross-Site Scripting (XSS) vulnerability in the WP Masonry & Infinite Scroll WordPress plugin, specifically in the 'wmis' shortcode handler. The vulnerability arises because the plugin insufficiently sanitizes and escapes user-supplied shortcode attributes, allowing authenticated users with contributor-level access or higher to inject arbitrary JavaScript code. This malicious code is then stored and executed whenever any user views the affected page, potentially compromising site security. [1, 2]


How can this vulnerability impact me? :

This vulnerability can allow an authenticated attacker with contributor-level access or above to inject malicious scripts into pages via the plugin's shortcode attributes. When other users visit these pages, the injected scripts execute in their browsers, potentially leading to session hijacking, defacement, unauthorized actions on behalf of users, or theft of sensitive information. This compromises the security and integrity of the affected WordPress site. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by identifying the presence of the vulnerable WordPress plugin 'wp-masonry-infinite-scroll' version 2.2 or earlier, and by checking for usage of the '[wmis]' shortcode with potentially malicious attributes. On the system, you can search for the plugin directory and check its version. Additionally, monitoring HTTP requests for suspicious shortcode usage or unusual 'wmis_page' GET parameters may help detect exploitation attempts. Example commands to detect the plugin and version on a WordPress installation include: 1. Check plugin version: grep -r 'Version:' wp-content/plugins/wp-masonry-infinite-scroll/ 2. Search for shortcode usage in posts/pages: grep -r '\[wmis' wp-content/uploads/ 3. Monitor web server logs for requests containing 'wmis_page' parameter or '[wmis]' shortcode payloads. Note: There are no specific built-in commands to detect the vulnerability automatically; detection relies on identifying the vulnerable plugin version and monitoring for suspicious shortcode usage or payloads. [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1. Update the 'wp-masonry-infinite-scroll' plugin to the latest version that includes the security fixes addressing CVE-2025-5488. 2. If updating is not immediately possible, disable or remove the plugin to prevent exploitation. 3. Review and sanitize any existing content using the '[wmis]' shortcode to ensure no malicious scripts are embedded. 4. Apply web application firewall (WAF) rules to block suspicious requests containing malicious shortcode attributes or unusual 'wmis_page' parameters. The update includes proper sanitization of shortcode attributes and pagination parameters, preventing stored XSS attacks as described in the changeset. [2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart