CVE-2025-61599
BaseFortify
Publication date: 2025-10-03
Last updated on: 2025-10-08
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| emlog | emlog | to 2.5.21 (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 "Twitter" feature of EMLOG Pro version 2.5.21 and below. An authenticated user with permission to post a "Twitter" message can inject arbitrary JavaScript code. This malicious script is stored on the server and executes in the browser of any user, including administrators, when they view the malicious post.
How can this vulnerability impact me? :
The vulnerability can allow attackers to execute arbitrary JavaScript in the browsers of users who view the malicious post. This can lead to session hijacking, theft of sensitive information, defacement, or other malicious actions performed in the context of the affected website, potentially compromising user accounts and site integrity.
What immediate steps should I take to mitigate this vulnerability?
Since there is no current fix for this vulnerability, immediate mitigation steps include restricting the privileges of users who can post "Twitter" messages to trusted individuals only, monitoring and reviewing all posts for suspicious content, and educating users to avoid clicking on untrusted or suspicious posts. Additionally, consider implementing web application firewall (WAF) rules to detect and block potential XSS payloads in posts.