CVE-2026-30879
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedbaserCMS is a website development framework. Prior to version 5.2.3, baserCMS has a cross-site scripting vulnerability in blog posts. This issue has been patched in version 5.2.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencebaserCMS prior to version 5.2.3 contains a cross-site scripting (XSS) vulnerability in its blog posts functionality. An attacker could inject malicious scripts into blog posts that would execute in the browsers of users viewing those posts, potentially allowing session hijacking or credential theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify baserCMS installationLocate baserCMS core files or configuration in your web directory. Common locations include checking for /config/install.php or a /baser directory in your web root.Affected if baserCMS is not found in your environment
-
Determine installed baserCMS versionCheck the baserCMS version file or admin dashboard for the current version number. This is typically displayed in the admin panel or in a VERSION file within the baserCMS installation.Affected if The installed version cannot be determined or is not visible
-
Verify blog plugin is enabledAccess the baserCMS admin panel and check if the blog plugin/posts functionality is installed and active. Navigate to the plugins or extensions section to confirm blog functionality status.Affected if The blog plugin is enabled and being used to publish content
-
Compare version against affected rangeCompare your installed baserCMS version to the affected range of versions prior to 5.2.3. If your version number is less than 5.2.3, you are within the affected range.Affected if Your baserCMS version is lower than 5.2.3
You are affected if baserCMS is installed with a version lower than 5.2.3 and the blog posts functionality is enabled and in use.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.2.3
Upgrade baserCMS to version 5.2.3 or later to apply the security patch that addresses this XSS vulnerability in blog posts.
5.2.3
- 1. Backup the current baserCMS installation and database before proceeding with the upgrade
- 2. Download baserCMS version 5.2.3 or later from the official source at basercms.net
- 3. Follow the official baserCMS upgrade documentation to apply the update
- 4. Verify the upgrade was successful by checking the admin panel and confirming the version number
- 5. Test that the blog post functionality works correctly and the XSS vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30879 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30879 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data