CVE-2003-0275
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 · uneditedSSI.php in YaBB SE 1.5.2 allows remote attackers to execute arbitrary PHP code by modifying the sourcedir parameter to reference a URL on a remote web server that contains the code.
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 confidenceSSI.php in YaBB SE 1.5.2 contains a remote file include (RFI) vulnerability via the sourcedir parameter, allowing remote attackers to execute arbitrary PHP code by pointing the parameter to a malicious remote URL containing PHP 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.5.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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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 YaBB SE installation and versionCheck the version file in your YaBB SE installation directory, typically found in a version.php or similar file, or check the YaBB SE admin panel for the installed version numberAffected if The installed version is YaBB SE 1.5.2 exactly
-
Locate SSI.php fileSearch for the SSI.php file in the web document root where YaBB SE is installedAffected if SSI.php exists in the YaBB SE installation directory and is web-accessible
-
Verify sourcedir parameter usage in SSI.phpOpen SSI.php and examine if the sourcedir parameter is used in include/require statements without proper sanitizationAffected if The sourcedir parameter is used in include() or require() statements without validation, allowing arbitrary URL injection
-
Check PHP allow_url_fopen settingReview php.ini or run phpinfo() to check if the PHP directive allow_url_fopen is enabledAffected if allow_url_fopen is set to On, which permits URL-aware fopen wrappers and enables remote file inclusion attacks
You are affected if YaBB SE 1.5.2 is installed, SSI.php is web-accessible, and the sourcedir parameter can be controlled externally, especially with allow_url_fopen enabled in PHP
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 dataUpgrade YaBB SE to a patched version, or disable the SSI.php file if unused; alternatively, disable allow_url_fopen and allow_url_include in PHP configuration to prevent remote file inclusion.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-0275 — 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-0275 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