CVE-2025-41021

CVSS 5.4 Medium
  • CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
  • Published: 2025-10-16T08:15:35.760

Stored Cross-Site Scripting (XSS) in Sergestec’s Exito v8.0, consisting of a stored XSS due to a lack of proper validation of user input by sending a POST request using the ‘obs’ parameter in ‘/admin/index.php?action=product_update’. This vulnerability could allow a remote user to send a specially crafted query to an authenticated user and steal their cookie session details.

Related CVE by CWE

No related CWE found.

Top CVE for Vendor

No vendor taxonomy on this entry.

Recently Exploited Similar Vulnerabilities

No recent KEV-listed items for this vendor/product.

How to fix CVE-2025-41021

CVE-2025-41021 is a medium severity vulnerability affecting the affected product.

Description: Stored Cross-Site Scripting (XSS) in Sergestec’s Exito v8.0, consisting of a stored XSS due to a lack of proper validation of user input by sending a POST request using the ‘obs’ parameter in ‘/admin/index.php?action=product_update’. This vulnerability could allow a remote user to send a specially crafted query to an authenticated user and steal their cookie […]

Exploit Difficulty: MEDIUM
⏱️ Time to exploit: 1-4 hours
🛠️ Required skills: Intermediate security knowledge
💰 Public exploits: May be available

How to Fix:

1 Identify affected systems

- Check if you're running the affected product

2 Immediate actions

- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access

3 Verification

- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)

4 Long-term prevention

- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations

Exploit Difficulty Assessment

MEDIUM
⏱️ Time to Exploit: 1-4 hours
🛠️ Skills Required: Intermediate security knowledge
💰 Public Exploits: May be available

Vulnerability Timeline

Oct 16, 2025
Vulnerability Published

CVE details first published to NVD database

Nov 12, 2025
Imported to Database

Added to this CVE tracking system

Detection Rules & IOCs

No specific detection rules generated for this vulnerability type.

No vendor/product data available.