Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112190 Overview
CVE-2026-112190 is an information disclosure vulnerability affecting Webkul Aureus ERP versions up to 1.6.0. The flaw resides in the handling of the composer.json file, which exposes sensitive information intended for debugging contexts. Attackers can retrieve the exposed data remotely without authentication or user interaction. The exploit has been publicly disclosed, increasing the likelihood of opportunistic abuse against unpatched deployments. The vulnerability is categorized under [CWE-200] Exposure of Sensitive Information to an Unauthorized Actor.
Critical Impact
Remote, unauthenticated attackers can harvest sensitive information from composer.json, exposing dependency details, internal paths, and configuration metadata that aid follow-on attacks.
Affected Products
- Webkul Aureus ERP versions through 1.6.0
- Deployments exposing the application composer.json file over HTTP
- Instances relying on default Webkul Aureus ERP web root configuration
Discovery Timeline
- 2026-10-19 - CVE-2026-112190 published to the National Vulnerability Database (NVD)
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-112190
Vulnerability Analysis
The vulnerability stems from the composer.json file being accessible to unauthenticated remote clients. Composer manifests describe PHP project dependencies, autoload paths, scripts, and sometimes environment-specific metadata. When the file is served directly by the web server, attackers can enumerate installed libraries, exact versions, and internal structure of the Aureus ERP application. This metadata narrows the attack surface for subsequent exploitation, including targeting of known vulnerable dependencies.
The CWE-200 classification confirms the root issue is information exposure rather than code execution. However, debug-oriented data embedded in the manifest can accelerate reconnaissance and support chained attacks against the ERP stack.
Root Cause
The root cause is improper web server configuration or application packaging that allows the composer.json manifest to be served as a static asset within the public document root. The file was not intended to be reachable by remote clients and contains data appropriate only for development or debugging contexts. No access control gates the request path, so any HTTP client can retrieve the content.
Attack Vector
The attack vector is network-based and requires no privileges or user interaction. An attacker issues a direct HTTP GET request for the composer.json path on an exposed Webkul Aureus ERP instance. The server returns the manifest contents, revealing dependency names, version constraints, autoload mappings, and any custom scripts. Attackers can automate discovery across internet-facing deployments using standard web crawlers or search engines indexing exposed JSON files. Technical details are documented in the GitHub Information Disclosure Report and the VulDB CVE-2026-112190 Details.
Detection Methods for CVE-2026-112190
Indicators of Compromise
- HTTP GET requests to /composer.json or similar manifest paths in web server access logs
- Requests originating from scanning infrastructure, cloud ranges, or automated crawlers targeting JSON configuration files
- Repeated enumeration attempts probing additional dependency metadata files such as composer.lock or .env
Detection Strategies
- Review web server access logs for successful 200 responses to requests for composer.json under the Aureus ERP document root
- Baseline normal application traffic patterns and alert on anomalous access to developer artifacts
- Correlate reconnaissance requests with subsequent exploitation attempts targeting dependencies referenced in the manifest
Monitoring Recommendations
- Enable Web Application Firewall (WAF) rules that block access to known development artifacts including composer.json, composer.lock, .git/, and .env
- Forward web server logs to a centralized SIEM for behavioral analysis and alerting on sensitive file access
- Schedule recurring external attack surface scans to detect inadvertently exposed configuration files
How to Mitigate CVE-2026-112190
Immediate Actions Required
- Restrict access to composer.json at the web server level by returning HTTP 403 or 404 for direct requests
- Relocate the Composer manifest outside the public document root where application architecture permits
- Audit the deployed composer.json content and rotate any secrets or internal identifiers that may have been exposed
Patch Information
No vendor patch has been referenced in the available advisory data at the time of publication. Operators should monitor the VulDB Vulnerability #422295 entry and Webkul release channels for a formal fix. Until a vendor update is published, enforce server-level filtering to block requests for development manifests.
Workarounds
- Add web server rules (for example, Nginx location or Apache <Files> directives) that deny public access to composer.json and related metadata files
- Deploy a WAF signature that blocks requests ending in composer.json, composer.lock, or other sensitive artifact names
- Remove debug-related entries from the manifest before deployment to production environments
# Nginx: block public access to Composer manifests and related artifacts
location ~* /(composer\.json|composer\.lock|\.env|\.git) {
deny all;
return 404;
}
# Apache (.htaccess): deny access to Composer metadata files
<FilesMatch "^(composer\.(json|lock)|\.env)$">
Require all denied
</FilesMatch>
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

