CVE-2003-1383
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWEB-ERP 0.1.4 and earlier allows remote attackers to obtain sensitive information via an HTTP request for the logicworks.ini file, which contains the MySQL database username and password.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencewebERP 0.1.4 and earlier exposes the logicworks.ini configuration file via direct HTTP request. This file contains MySQL database credentials (username and password) stored in plaintext, allowing remote attackers to obtain database authentication credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Logicworks Web ERP is installedCheck your web server's document root for the webERP application files, typically in a directory named 'weberp', 'webERP', or similar. Look for the presence of PHP files belonging to the application.Affected if Logicworks Web ERP is present on the server
-
Determine the installed versionCheck for a version file, header comment in PHP files, or the logicworks.ini file itself for a version indicator. Common locations include the root directory of the application or the logicworks.ini file.Affected if Version is 0.1.4 or earlier
-
Test HTTP access to logicworks.iniUsing a web browser or curl command, attempt to access http://your-server/path/to/weberp/logicworks.ini (adjust path as needed for your installation). A successful HTTP 200 response means the file is exposed.Affected if The file returns HTTP 200 and is downloadable via direct HTTP request
-
Verify file contains plaintext credentialsIf logicworks.ini is accessible, examine its contents to confirm it contains MySQL database credentials (username and password fields).Affected if The file contains plaintext MySQL username and password
If Logicworks Web ERP version 0.1.4 or earlier is installed and the logicworks.ini file is accessible via HTTP, the environment is affected as database credentials can be harvested by remote attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataMove logicworks.ini outside the web document root directory, or configure the web server to deny HTTP access to .ini files. Verify the file is no longer accessible via HTTP.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-1383 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2003-1383 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data