Skip to content

GHSA-q57g-38pc-jwv8 CVE-2023-5976

Microweber Improper Access Control vulnerability

Medium Packagist
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.39%
Chance of exploitation in the next 30 days. Higher than 33.57% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
2.0.0
Upgrade microweber/microweber to this version or later

Description

Improper Access Control in GitHub repository microweber/microweber prior to 2.0.0.

Affected versions

Packagist

PackageVulnerableFixed in
microweber/microweber
< 2.0.0
2.0.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

microweber/microweber Packagist → 2.0.0

composer
composer require microweber/microweber:^2.0.0

Severity breakdown

CVSS 3.1 4.3

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

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

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • 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-vv4x-qcpq-wgrg
Microweber vulnerable to Path Traversal
High Also affects microweber/microweber
GHSA-6w5w-jx4x-vjvw
Microweber Cross-site Scripting vulnerability
Medium Also affects microweber/microweber
GHSA-5jg5-xqfw-rv92
Microweber has a Cross-site Scripting vulnerability
Medium Also affects microweber/microweber
GHSA-2x2j-3c2v-g3c2
Microweber XSS Vulnerability in the homepage Endpoint
High Also affects microweber/microweber
GHSA-mvj3-hc7j-vp74
Microweber has Reflected XSS Vulnerability in the layout Parameter
Medium Also affects microweber/microweber
GHSA-8357-fjvx-xrm8
Microweber has Reflected XSS Vulnerability in the id Parameter
Medium Also affects microweber/microweber
GHSA-782f-gxj5-xvqc
Microweber Has Stored XSS Vulnerability in User Profile Fields
High Also affects microweber/microweber
GHSA-j64v-xh5w-8hqj
Microweber CMS API has authenticated local file inclusion vulnerability
High Also affects microweber/microweber
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