CVE-2025-9541
BaseFortify
Publication date: 2025-09-22
Last updated on: 2025-09-22
Assigner: WPScan
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | markup_markdown | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9541 is a Stored Cross-Site Scripting (XSS) vulnerability in the WordPress plugin Markup Markdown versions before 3.20.10. It allows users with the Contributor role or higher to inject malicious JavaScript code into links within posts. When these posts are viewed, the injected JavaScript executes, potentially compromising the security of users viewing the content. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers with Contributor-level access to inject malicious JavaScript into posts, which executes when other users view the posts. This can lead to unauthorized actions such as stealing session cookies, defacing content, or performing actions on behalf of other users, thereby compromising the security and integrity of the website and its users. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the installed version of the Markup Markdown WordPress plugin is prior to 3.20.10. Additionally, testing for the vulnerability can be done by attempting to insert a payload similar to `[![Uh oh...]("onerror=alert('XSS'))` in a post as a user with Contributor role or higher and then viewing the post to see if the JavaScript executes. There are no specific network commands provided, but verifying plugin version and testing input sanitization in posts are key steps. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the Markup Markdown WordPress plugin to version 3.20.10 or later, where the vulnerability is fixed. Additionally, restricting or reviewing user roles and permissions to limit who can create or edit posts with links may help reduce risk until the update is applied. [1]