CVE-2025-10274

4.3 MEDIUM

📋 TL;DR

This CVE describes a cross-site scripting (XSS) vulnerability in erjinzhi 10OA 1.0 software. Attackers can inject malicious scripts via the Name parameter in the /trial/mvc/item endpoint, potentially compromising user sessions or stealing sensitive data. Organizations using erjinzhi 10OA 1.0 are affected.

💻 Affected Systems

Products:
  • erjinzhi 10OA
Versions: 1.0
Operating Systems: Unknown
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability affects unknown functionality in the specified endpoint. Default installations appear vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, hijack user sessions, deface websites, or redirect users to malicious sites, potentially leading to complete system compromise.

🟠

Likely Case

Attackers would typically steal session cookies or user credentials, enabling unauthorized access to the affected application.

🟢

If Mitigated

With proper input validation and output encoding, the impact would be limited to unsuccessful exploitation attempts.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The exploit has been released publicly and may be exploited. Attack can be initiated remotely without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Vendor was contacted but did not respond. Consider workarounds or alternative software.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize the Name parameter, rejecting or encoding malicious scripts.

Implement input validation in /trial/mvc/item endpoint

Web Application Firewall (WAF)

all

Deploy a WAF with XSS protection rules to block malicious requests to the vulnerable endpoint.

Configure WAF to block requests containing script tags or XSS patterns

🧯 If You Can't Patch

  • Isolate the affected system from the internet and restrict access to trusted networks only.
  • Implement strict Content Security Policy (CSP) headers to mitigate XSS impact.

🔍 How to Verify

Check if Vulnerable:

Test the /trial/mvc/item endpoint with XSS payloads in the Name parameter to see if scripts execute.

Check Version:

Check application version through admin interface or configuration files.

Verify Fix Applied:

Retest with XSS payloads after implementing workarounds to ensure scripts are blocked or sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual requests to /trial/mvc/item with script tags or encoded payloads in Name parameter

Network Indicators:

  • HTTP requests containing malicious script patterns targeting the vulnerable endpoint

SIEM Query:

source="web_logs" AND uri="/trial/mvc/item" AND (query="*<script>*" OR query="*javascript:*")

🔗 References

📤 Share & Export