CVE-2004-0031
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 · uneditedPHPGEDVIEW 2.61 allows remote attackers to reinstall the software and change the administrator password via a direct HTTP request to editconfig.php.
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 confidencePHPGEDVIEW 2.61 contains an installation and configuration vulnerability where the editconfig.php script lacks proper authentication or authorization checks, allowing remote attackers to directly access the file and trigger a reinstallation of the application. This enables them to set a new administrator password and gain full administrative control over the PHPGEDVIEW instance.
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= 2.61CVSS 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 PHPGEDVIEW versionLocate the version file or header in the PHPGEDVIEW installation directory. Common locations include a version.php file, README, or the main index page footer which often displays the version number.Affected if The installed version is 2.61 (exact match to the affected version)
-
Verify editconfig.php existsCheck if the editconfig.php script file exists in the web root or installation directory of PHPGEDVIEW. Use file system inspection or a web request to the known path (e.g., GET /editconfig.php).Affected if The file editconfig.php exists in the accessible web directory
-
Test editconfig.php unauthenticated accessSend an HTTP request to editconfig.php without providing any authentication credentials. Observe whether the script executes or returns configuration/reinstallation options rather than redirecting to a login page or denying access.Affected if editconfig.php executes and displays configuration or installation options without requiring authentication
-
Check installation stateExamine whether the application considers itself already installed. This may be indicated by the presence of a config file, a database connection file, or a flag in the application. Try accessing editconfig.php to see if reinstallation options are presented.Affected if The application allows reinstallation through editconfig.php without any authentication, meaning the script is reachable and functional
A user is affected if they have PHPGEDVIEW version 2.61 installed with editconfig.php accessible without any authentication, allowing unauthorized reconfiguration of the application.
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 dataRemove or restrict access to installation scripts including editconfig.php after initial setup, and implement proper authentication checks before allowing any configuration modifications.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0031 — 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-0031 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