CVE-2019-17130
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 · uneditedvBulletin through 5.5.4 mishandles external URLs within the /core/vb/vurl.php file and the /core/vb/vurl directories.
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 confidencevBulletin through 5.5.4 contains a vulnerability in its URL handling within /core/vb/vurl.php and /core/vb/vurl directories where external URLs are mishandled, potentially allowing manipulation of URL processing logic.
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<= 5.5.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 vBulletin installation versionLocate the version file in your vBulletin installation (typically includes/version.php or check the admin control panel About section). Extract the numeric version number.Affected if The installed version is 5.5.4 or any earlier version (5.0.0 through 5.5.4 are all affected)
-
Verify affected vurl.php file existsCheck for the presence of the file /core/vb/vurl.php in your vBulletin installation directory. This file contains the vulnerable URL handling logic.Affected if The file /core/vb/vurl.php exists and contains URL processing code (the vulnerability is in this file)
-
Check vurl directory for URL processing modulesExamine the /core/vb/vurl/ directory for any PHP files that handle external URL processing or URL validation.Affected if The /core/vb/vurl/ directory contains URL handler classes or modules that process external URLs
-
Identify URL handling configuration or usageSearch the vurl.php file for functions that handle, parse, or validate external URLs. Look for methods that process user-supplied or external URL inputs.Affected if URL handling functions in vurl.php process external/remote URLs without strict validation
-
Confirm active URL processing functionalityReview your vBulletin configuration to determine if URL-based features are enabled (such as URL embedding, external link rendering, or any feature that fetches/processes external URLs).Affected if URL processing features are enabled and the vurl.php file is actively used for handling external URLs
You are affected if your vBulletin installation is version 5.5.4 or earlier and the /core/vb/vurl.php file with URL handling logic is present and actively processing external URLs.
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 to a patched version of vBulletin. If no patch is available, implement strict input validation and whitelisting for URL parameters in the affected vurl.php file and vurl directory.
- 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-2019-17130 — 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-2019-17130 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