Skip to content

GHSA-w935-p7mg-xc96 CVE-2018-0575

Sensitive Data Exposure in baserCMS

Medium Packagist
Severity
5.3 / 10
Medium · CVSS 3.0
Exploit chance (EPSS)
1.18%
Chance of exploitation in the next 30 days. Higher than 67.73% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
None yet
No fixed version published

Description

baserCMS (baserCMS 4.1.0.1 and earlier versions, baserCMS 3.0.15 and earlier versions) allows remote attackers to bypass access restriction in mail form to view a file which is uploaded by a site user via unspecified vectors.

Affected versions

Packagist

PackageVulnerableFixed in
baserproject/basercms
>= 4.0.0, <= 4.1.0.1
No fix yet
baserproject/basercms
<= 3.0.15
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.0 5.3

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-677c-xv24-crgx
baserCMS is Vulnerable to Cross-site Scripting
Medium Also affects baserproject/basercms
GHSA-c5c6-37vq-pjcq
baserCMS Path Traversal Leads to Arbitrary File Write and RCE via Theme File API
High Also affects baserproject/basercms
GHSA-6hpg-8rx3-cwgv
baserCMS has OS command injection vulnerability in installer
Critical Also affects baserproject/basercms
GHSA-jmq3-x8q7-j9qm
baserCMS has a cross-site scripting vulnerability in blog posts
Medium Also affects baserproject/basercms
GHSA-8cr7-r8qw-gp3c
baserCMS has Mail Form Acceptance Bypass via Public API
Medium Also affects baserproject/basercms
GHSA-m9g7-rgfc-jcm7
baserCMS Update Functionality Vulnerable to OS Command Injection
High Also affects baserproject/basercms
GHSA-vh89-rjph-2g7p
baserCMS has an SQL injection vulnerability in its blog post functionality
Critical Also affects baserproject/basercms
GHSA-qxmc-6f24-g86g
baserCMS has OS Command Injection Leading to Remote Code Execution (RCE)
High Also affects baserproject/basercms
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor