CVE-2019-25270
Cross-Site Scripting in SOCA Access Control logged_page.php
Publication date: 2026-01-08
Last updated on: 2026-01-08
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| soca_technology_co_ltd | soca_access_control_system | 180612 |
| soca_technology_co_ltd | soca_access_control_system | 170000 |
| soca_technology_co_ltd | soca_access_control_system | 141007 |
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 reflected Cross-Site Scripting (XSS) flaw in the SOCA Access Control System version 180612. It occurs because the 'senddata' POST parameter in the 'logged_page.php' script does not properly sanitize user input. Attackers can exploit this by sending specially crafted POST requests that inject and execute arbitrary HTML and JavaScript code within a victim's browser session, potentially leading to unauthorized actions or data exposure. [1, 2]
How can this vulnerability impact me? :
Exploiting this vulnerability allows attackers to execute arbitrary scripts in the context of a user's browser session. This can lead to theft of sensitive information, session hijacking, or performing unauthorized actions on behalf of the user. Although the risk level is considered low to moderate, the vulnerability is remotely exploitable without requiring local access, which increases the attack surface. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted POST requests to the 'logged_page.php' endpoint with malicious payloads in the 'senddata' parameter and observing if the injected script executes in the response. For example, you can use curl to send a test payload like: curl -X POST -d "senddata=<script>alert(1)</script>" http://target/logged_page.php and check if the alert script executes or appears in the response. This indicates the presence of the reflected XSS vulnerability. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all user inputs, especially the 'senddata' POST parameter, to prevent injection of malicious scripts. Applying input filtering or encoding output to neutralize HTML and JavaScript code is essential. Additionally, restricting access to the vulnerable endpoint and updating or patching the SOCA Access Control System to a version where this vulnerability is fixed are recommended. [1, 2]