CVE-2025-13863
BaseFortify
Publication date: 2025-12-06
Last updated on: 2025-12-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| krupenik | revinsite | 1.1.0 |
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 RevInsite WordPress plugin up to version 1.1.0. It occurs because the plugin does not properly sanitize or escape input in the 'token' parameter. As a result, authenticated users with Contributor-level access or higher can inject malicious scripts that will execute whenever other users view the affected pages.
How can this vulnerability impact me? :
The vulnerability allows attackers with Contributor-level access to inject malicious scripts into pages, which can then 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 victim user.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can involve searching for the presence of the RevInsite plugin version 1.1.0 or earlier on your WordPress installation and checking for usage of the `token` parameter in stored content. Since the vulnerability involves stored Cross-Site Scripting via the `token` parameter, you can scan your WordPress database for suspicious script tags or unusual JavaScript injections in posts or pages. Additionally, monitoring HTTP requests and responses for injected scripts related to RevInsite's `token` parameter may help. Specific commands are not provided in the resources. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the RevInsite plugin to a version later than 1.1.0 once available, or temporarily disabling the plugin to prevent exploitation. Restrict Contributor-level and above users from adding or modifying content that includes the `token` parameter until a patch is applied. Review and sanitize any stored content that may contain malicious scripts injected via the `token` parameter. Since the plugin manages the token via an admin settings page accessible only to users with `manage_options` capability, ensure that only trusted administrators have access to this page. [2]