CVE-2004-0697
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 · uneditedUnknown vulnerability in 4D WebSTAR 5.3.2 and earlier allows remote attackers to read the php.ini configuration file and possibly obtain sensitive information.
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 · moderate confidenceAn information disclosure vulnerability in 4D WebSTAR 5.3.2 and earlier allows remote attackers to read the php.ini configuration file, potentially exposing sensitive information such as database credentials, API keys, or other configuration details.
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= 4.0= 5.2= 5.2.1= 5.2.2= 5.2.3= 5.2.4= 5.3= 5.3.1= 5.3.2CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 4D WebSTAR is installedCheck the server for 4D WebSTAR installation directories or services. Common locations may include /Library/WebServer/Documents or application-specific directories. Look for the WebSTAR application or service running on common web ports (80, 443).Affected if 4D WebSTAR is found running on the system
-
Determine the installed versionLocate version information in the WebSTAR application, its configuration files, or by querying the running service. Compare the version number against the affected list: 4.0, 5.2, 5.2.1, 5.2.2, 5.2.3, 5.2.4, 5.3, 5.3.1, 5.3.2Affected if The installed version matches any of the affected versions listed
-
Check if php.ini is web-accessibleAttempt to access php.ini via HTTP/HTTPS requests to the web server using common paths such as /php.ini, /..php.ini, or the document root path. Use web vulnerability scanning tools or manual curl requests to test for disclosure.Affected if The php.ini file is reachable over the network via the web server
-
Inspect web server configurationReview WebSTAR configuration files for directory access controls, alias mappings, or MIME type settings that could allow serving php.ini files as plain text.Affected if Configuration permits .ini files to be served as downloadable content
-
Verify network exposureDetermine if the WebSTAR server is directly accessible from untrusted networks. Check firewall rules, ACLs, and network perimeter configurations.Affected if The server accepts external connections from untrusted networks
The environment is affected if 4D WebSTAR version 5.3.2 or earlier is running and the php.ini file is accessible via HTTP/HTTPS requests from the network.
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 dataSince 4D WebSTAR is obsolete software, the primary remediation is to migrate to a supported web server platform. If immediate migration is not feasible, restrict network access to the server and verify that php.ini files are not accessible via the web server.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0697 — 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-2004-0697 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