CVE-2025-5289
BaseFortify
Publication date: 2025-06-21
Last updated on: 2025-07-09
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 3dflipbook | 3d_flipbook | to 1.16.15 (inc) |
Helpful Resources
Exploitability
| 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?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the 3D FlipBook WordPress plugin. It occurs because the plugin does not properly sanitize and escape input parameters, specifically the 'style' and 'mode' parameters, in versions up to and including 1.16.15. Authenticated users with Contributor-level access or higher can inject malicious scripts into pages. These scripts then execute whenever any user views the affected page, potentially compromising user data or site integrity. The issue affects only block-based WordPress themes. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow attackers with Contributor-level access or higher to inject arbitrary JavaScript into pages, which will execute in the browsers of users who visit those pages. This can lead to theft of user credentials, session hijacking, defacement, or other malicious actions performed on behalf of the user. Since the vulnerability is stored, the malicious script persists on the site until removed or patched, potentially affecting many users. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying if the WordPress site is running the 3D FlipBook plugin version 1.16.15 or earlier, which is vulnerable to stored cross-site scripting via the 'style' and 'mode' parameters. Detection can involve checking plugin versions and scanning for injected scripts in pages accessible by users with Contributor-level access or higher. Specific commands are not provided in the resources, but typical detection steps include: 1) Using WP-CLI to check the plugin version: `wp plugin list --status=active` and verify the version of the 3D FlipBook plugin. 2) Searching the database for suspicious script injections in post content or plugin-related data fields, e.g., using SQL queries to find occurrences of script tags or suspicious 'style' or 'mode' parameter values. 3) Using web vulnerability scanners that detect stored XSS in WordPress plugins. However, no explicit commands are detailed in the provided resources. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the 3D FlipBook plugin to version 1.16.16 or later, where the issue has been fixed by improving parameter escaping using WordPress's native esc_attr() function to prevent stored cross-site scripting attacks. Additionally, ensure that only trusted users have Contributor-level or higher access, and consider reviewing and sanitizing any content that may have been injected with malicious scripts. Applying the official patch or update from the plugin repository is the recommended mitigation. [1]