Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 05:05 UTC

Critical in the last 24 hours

1602 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

161-73% vs 7-day avg of 598

2 critical, 47 high, 62 medium, 30 low

Expand	Severity	Score	Advisory	Title	Source	Published
	Medium	6.5	CVE-2026-114623	baserCMS is a website development framework baserproject, baserCMSbaserproject basercms, baserCMS, baserCMS bc-theme-file	NVD	Oct 23 14:17 UTC
CVE-2026-114623baserCMS is a website development framework From the advisory baserCMS is a website development framework. In versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2, an authenticated user with only theme-file view permission can traverse outside the theme directory through the optional BcThemeFile plugin's Admin web screen. ThemeFilesController::parseArgs() constructs a path containing literal ../ segments, and the view and edit actions pass it to ThemeFilesService::get() without containment validation. Authorization checks the unresolved request path, after which ThemeFile::_getContents() reads the resolved file and exposes its contents in the form textarea. A client must preserve the dot segments rather than normalize them away. Readable files are limited to .php, .css, .js, and .ctp; this can disclose application source and config/install.php database credentials in MySQL or PostgreSQL deployments, while SQLite configurations have an empty database password. Reading config/app_local.php may expose the Security.salt fallback, which is effective only when not overridden by environment configuration. The flaw does not disclose .env, .pem, or SQLite .db files, does not itself permit file writes or code execution, and does not affect the separate API getFullpath() route. The plugin is disabled by default and unauthenticated requests are not sufficient. This issue has been patched in versions 5.3.2 and 5.4.2. Impact if exploited ConfidentialityHigh IntegrityNone AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Privileges required Low User interaction None Scope Unchanged CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Affects baserproject baserCMS baserproject basercms baserCMS baserCMS bc-theme-file NIST National Vulnerability DatabasePublished Oct 23, 2026 14:17 UTC Read the advisory
	High	7.2	CVE-2026-114622	baserCMS is a website development framework baserproject, baserCMSbaserproject basercms, baserCMS bc-theme-file	NVD	Oct 23 14:17 UTC
CVE-2026-114622baserCMS is a website development framework Executive summary The advisory describes a path traversal flaw in baserCMS, a website development framework, that let requests reach files outside the theme directory, including reading and copying files on the server. The advisory text provided shows code changes that add path boundary checks, but it does not state a severity rating, and no CVSS score is stated. The advisory provides a patch as its remedy, and it does not state a workaround. Technical summary The flaw is a path traversal weakness (CWE class not stated) in the theme file management plugin bc-theme-file. Admin web routes built the fullpath from URL input without the boundary check used by the API route, so a path containing dot-dot segments could read images, copy source files into the current theme webroot, and write or rename files outside the theme. The attack requires an authenticated admin session, which the diff implies through the admin routes but the advisory does not explicitly state. The fix adds boundary checks in ThemeFilesController::parseArgs, BcThemeFileService, ThemeFilesService and ThemeFoldersService, and checks decoded paths as well. Affected and fixed version numbers are not stated, and no workaround or detection guidance is stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/baserproject/basercms/commit…c4b42d313983329aa162 Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Network Attack complexity Low Privileges required High User interaction None Scope Unchanged CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Affects baserproject baserCMS baserproject basercms baserCMS bc-theme-file NIST National Vulnerability DatabasePublished Oct 23, 2026 14:17 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

From the advisory

Impact if exploited

How it is exploited

Affects

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee