CVE-2018-25168
CSRF Vulnerability in Precurio Portal Allows Admin Account Creation
Publication date: 2026-03-06
Last updated on: 2026-03-06
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| precurio | precurio_intranet_portal | 2.0 |
| precurio | intranet_portal | 2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2018-25168 is a Cross-Site Request Forgery (CSRF) vulnerability in Precurio Intranet Portal version 2.0. It allows unauthenticated attackers to create administrative user accounts by sending specially crafted POST requests to the /public/admin/user/submitnew endpoint. This endpoint processes user creation parameters without requiring CSRF tokens or any user interaction, enabling attackers to add new admin accounts without authorization.
The vulnerability exploits the lack of CSRF protections in the user creation functionality, allowing privilege escalation by bypassing authentication controls.
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'This vulnerability can have serious security impacts by allowing attackers to create new administrative user accounts without authorization. This unauthorized privilege escalation compromises the integrity and security of the affected system.'}, {'type': 'list_item', 'content': 'Attackers can gain administrative access to the portal.'}, {'type': 'list_item', 'content': 'They can potentially control or manipulate sensitive data and system settings.'}, {'type': 'list_item', 'content': "The system's security posture is weakened due to the bypass of authentication and CSRF protections."}] [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring for unauthorized POST requests to the endpoint /public/admin/user/submitnew that include user creation parameters such as user_id, first_name, last_name, email, password, department_id, and location_id.'}, {'type': 'paragraph', 'content': 'One way to detect exploitation attempts is to analyze web server logs for suspicious POST requests to this endpoint that result in a 302 redirect to the user edit page, which indicates successful creation of a new user.'}, {'type': 'paragraph', 'content': 'Network intrusion detection systems (NIDS) or web application firewalls (WAF) can be configured to alert on POST requests to /public/admin/user/submitnew without valid CSRF tokens.'}, {'type': 'paragraph', 'content': 'Example commands to detect such activity could include using grep on web server logs to find POST requests to the vulnerable endpoint:'}, {'type': 'list_item', 'content': "grep 'POST /public/admin/user/submitnew' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': "grep 'POST /public/admin/user/submitnew' /var/log/nginx/access.log"}, {'type': 'paragraph', 'content': 'Additionally, inspecting the POST request payloads for user creation parameters can help confirm attempts to exploit the vulnerability.'}] [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing CSRF protection mechanisms on the /public/admin/user/submitnew endpoint to require valid CSRF tokens for user creation requests.
Restrict access to the vulnerable endpoint to authenticated and authorized users only, ensuring that unauthenticated attackers cannot submit user creation requests.
Monitor and block suspicious POST requests targeting the endpoint, especially those that attempt to create new administrative users.
If possible, apply any available patches or updates from the software vendor that address this vulnerability.
As a temporary workaround, consider disabling the user creation functionality or restricting it via firewall rules until a proper fix is applied.