CVE-2018-0573
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 · uneditedbaserCMS (baserCMS 4.1.0.1 and earlier versions, baserCMS 3.0.15 and earlier versions) allows remote attackers to bypass access restriction for a content to view a file which is uploaded by a site user via unspecified vectors.
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 confidencebaserCMS contains an access restriction bypass vulnerability that allows remote attackers to view files uploaded by site users that should be protected. The vulnerability affects baserCMS 4.1.0.1 and earlier as well as baserCMS 3.0.15 and earlier versions, enabling unauthorized access to uploaded content through unspecified vectors.
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>= 3.0.0, <= 3.0.15> 4.0.0, <= 4.1.0.1CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed baserCMS versionCheck the version file or admin panel. Common locations: /lib/Baser/Config/version.php (3.x) or /vendor/baser/core/config/version.php (4.x). Alternatively, log into the admin dashboard and look at the footer or system info page.Affected if The installed version falls within 3.0.0 to 3.0.15 inclusive, or 4.0.1 to 4.1.0.1 inclusive.
-
Confirm file upload functionality is in useCheck if user uploads are enabled. Look for the Uploader plugin or upload behavior. Inspect /app/Plugin/Uploader/ (3.x) or /plugins/uploader/ (4.x) directory for presence and configuration files. Check config files for 'Uploader' plugin enablement.Affected if The Uploader plugin or any user-upload functionality is installed and active on the baserCMS instance.
-
Inspect upload directory access controlsExamine the web server configuration and the permissions on the files/Uploads or /app/webroot/files/uploads directory. Attempt to access a known uploaded file directly via browser URL without authentication to test access restrictions.Affected if Uploaded files are directly accessible via web browser without authentication or proper access controls.
-
Review .htaccess or web server access rulesCheck for .htaccess files in upload directories that should restrict direct access. Look for directives like 'Deny from all' or 'Require all denied' in the upload folder configuration.Affected if No access restrictions exist in .htaccess or web server config for upload directories, allowing unrestricted file retrieval.
You are affected if your baserCMS version is 3.0.0-3.0.15 or 4.0.1-4.1.0.1 and the file upload feature is enabled, with uploaded files accessible without authentication.
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 baserCMS 4.1.1 or later (for 4.x) or baserCMS 3.0.16 or later (for 3.x) to address the access control bypass. If upgrading is not immediately possible, review and restrict file access controls for user-uploaded content at the web server or application layer.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0573 — 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-2018-0573 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