CVE-2003-0395
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 · uneditedUltimate PHP Board (UPB) 1.9 allows remote attackers to execute arbitrary PHP code with UPB administrator privileges via an HTTP request containing the code in the User-Agent header, which is executed when the administrator executes admin_iplog.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 confidenceUltimate PHP Board (UPB) 1.9 has a remote code execution vulnerability where arbitrary PHP code embedded in the User-Agent HTTP header is stored and later executed when an administrator accesses the admin_iplog.php page. The attacker gains UPB administrator-level privileges to execute the injected code.
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= 1.9CVSS 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 UPB is installedLook for directories or files containing 'upb', 'ultimate php board', or 'myupb' in the web root. Common locations include /upb/, /forum/, or similar paths.Affected if UPB installation directory exists on the server
-
Confirm the installed versionCheck for version information in source files, typically in a config.php, version.php, or README file within the UPB installation directory. Compare the version number to 1.9.Affected if The installed version is exactly 1.9
-
Check if admin_iplog.php existsLocate the admin_iplog.php file within the UPB admin directory or web root. Verify the file is present and readable.Affected if admin_iplog.php file exists in the installation
-
Determine if HTTP header logging is activeReview UPB configuration files (config.php, settings.php) for logging-related settings. Look for options that enable logging of User-Agent or HTTP headers.Affected if User-Agent or HTTP header logging is enabled in UPB configuration
-
Inspect stored data for suspicious contentExamine database tables or log files that store User-Agent values. Look for PHP code patterns such as '<?php', 'system(', 'exec(', or base64-encoded strings in what should be plain text fields.Affected if Stored User-Agent data contains PHP code or suspicious script patterns
A user is affected if UPB version 1.9 is installed, the admin_iplog.php file exists, and User-Agent logging is enabled with potentially malicious stored content.
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 dataSanitize and validate all HTTP headers, particularly User-Agent, before storing or displaying them. Input should be treated as untrusted and escaping should be applied when output. Consider upgrading to a supported version of the software if available.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-0395 — 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-0395 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