Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3

Sensitive Data Exposure in baserCMS

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

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist baserproject/basercms

    Affected
    >= 4.0.0, <= 4.1.0.1<= 3.0.15
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2018-0575: 1.16% estimated exploitation activity in the next 30 days; percentile 67.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-w935-p7mg-xc96

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-0575

Advisory: Sensitive Data Exposure in baserCMS
IDs: CVE-2018-0575, GHSA-w935-p7mg-xc96
Record: https://patchnext.com/advisories/cve-2018-0575 (revision 1, source checked 26 Oct 2026, 14:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist baserproject/basercms: affected >= 4.0.0, <= 4.1.0.1; <= 3.0.15

## Suggested inspection (read-only)
- Packagist baserproject/basercms: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on baserproject/basercms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w935-p7mg-xc96 (GitHub-reviewed advisory GHSA-w935-p7mg-xc96 lists affected ranges: Packagist baserproject/basercms >=4.0.0 =0 <=3.0.15)

Commands are suggestions: review each one before running it.

Loading voting…