baserCMS Access Control Bypass
CVE-2015-5640GHSA-v9gf-98vr-mgp2
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (baserproject/basercms 3.0.8), redeploy, then verify what is actually installed.
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.
Affected packages
Packagist baserproject/basercms
- Affected
- <= 3.0.7
- Fixed in
- 3.0.8
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-v9gf-98vr-mgp2 lists affected ranges: Packagist baserproject/basercms >=0 <=3.0.7
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- CVE-2015-5640: 1.55% estimated exploitation activity in the next 30 days; percentile 75.13 (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 before 3.0.8 allows remote authenticated users to modify arbitrary user settings via a crafted request.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-v9gf-98vr-mgp2
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-2015-5640 Advisory: baserCMS Access Control Bypass IDs: CVE-2015-5640, GHSA-v9gf-98vr-mgp2 Record: https://patchnext.com/advisories/cve-2015-5640 (revision 1, source checked 26 Oct 2026, 14:06 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: baserproject/basercms 3.0.8. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist baserproject/basercms: affected <= 3.0.7; fixed in 3.0.8 ## Suggested inspection (read-only) - Packagist baserproject/basercms: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## 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-v9gf-98vr-mgp2 (GitHub-reviewed advisory GHSA-v9gf-98vr-mgp2 lists affected ranges: Packagist baserproject/basercms >=0 <=3.0.7) Commands are suggestions: review each one before running it.
Loading voting…