CVE-2024-46996
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. Versions prior to 5.1.2 have a cross-site scripting vulnerability in the Blog posts feature. Version 5.1.2 fixes this issue.
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 versions prior to 5.1.2 contain a cross-site scripting (XSS) vulnerability in the Blog posts feature. This allows attackers to inject malicious scripts through blog post content that executes in the browsers of other users viewing the affected pages.
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.1.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 the baserCMS installation directory on your server and check for version indicators such as a version file, composer.json, or the admin dashboard footer which typically displays the version numberAffected if baserCMS is installed and the version displayed is below 5.1.2
-
Confirm the Blog plugin is enabledAccess the baserCMS admin panel, navigate to the Plugins or System settings section, and verify whether the Blog plugin is installed and enabledAffected if The Blog plugin is active on the system
-
Check for existing blog postsNavigate to the Blog feature in the admin panel or inspect the database table that stores blog posts (typically named something like bc_blog_posts or similar) to see if any posts have been createdAffected if There are blog posts present in the system
-
Review blog post content for script tagsExamine the stored content of blog posts, either through the admin interface or by inspecting the database, looking for any <script> tags, javascript: URIs, or event handler attributes (onclick, onerror, etc.) that were not intentionally addedAffected if Any blog post content contains untrusted or suspicious script injections
You are affected if baserCMS is installed with a version prior to 5.1.2 AND the Blog plugin is enabled with existing posts that may contain malicious script injections
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.1.2
Upgrade baserCMS to version 5.1.2 or later to obtain the patch for this XSS vulnerability in the Blog posts feature.
5.1.2
- Backup the existing Basercms installation and database
- Download baserCMS version 5.1.2 from the official source (basercms.net or github.com)
- Follow the official upgrade documentation to install version 5.1.2
- Verify the blog posts feature is functioning correctly after upgrade
- Confirm the XSS vulnerability is resolved by testing blog post content input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46996 — 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-2024-46996 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