dbcve.org
BasercmsApplication

CVE-2024-46994

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-24
Fix available
A fix is available. Upgrade to 5.1.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
baserCMS is a website development framework. Versions prior to 5.1.2 have a cross-site scripting vulnerability in Blog posts and Contents list 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 · moderate confidence

baserCMS versions prior to 5.1.2 contain a cross-site scripting (XSS) vulnerability in the Blog posts and Contents list Feature. This allows attackers to inject malicious scripts through these components, which execute in the browsers of users viewing the affected content.

MitigationUpgrade baserCMS to version 5.1.2 or later to obtain the security patch for this XSS vulnerability.

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
BasercmsApplication
Affected:< 5.1.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify baserCMS installation location
    Look for baserCMS installation directories, typically found in web root folders. Check for the presence of baserCMS core files such as 'baser.php', 'config.php', or the '/baser' folder.
    Affected if baserCMS is installed on the system
  2. Determine installed baserCMS version
    Check the version file or admin dashboard. Common locations include: a VERSION file in the root directory, or log into the admin panel and navigate to System > Site Information to view the version number.
    Affected if The installed version is lower than 5.1.2 (e.g., 5.1.1, 5.1.0, 5.0.x, etc.)
  3. Verify Blog posts feature is active
    Check if the Blog plugin is enabled in baserCMS. Log into the admin panel and navigate to Plugins > Installed Plugins, or inspect the /plugins/BcBlog directory exists and is activated in the database.
    Affected if The Blog posts feature is enabled and accessible to users
  4. Verify Contents list feature is in use
    Check if the Contents List (BcContentsList) widget or element is being used in themes. Inspect theme templates for calls to $this->BcContents->getList() or similar content list components, or check widget configurations in the admin panel.
    Affected if The Contents list feature is implemented in active themes or pages

The environment is affected if baserCMS version is below 5.1.2 AND either the Blog posts or Contents list feature is actively used on the site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.1.2 or later
Fixed in 5.1.2
Interim mitigation

Upgrade baserCMS to version 5.1.2 or later to obtain the security patch for this XSS vulnerability.

Recommended fix High confidence

Basercms 5.1.2

  1. 1. Backup your existing Basercms installation and database before proceeding
  2. 2. Download Basercms version 5.1.2 from the official Basercms repository (github.com/basercms/basercms)
  3. 3. Replace the existing Basercms files with the new version 5.1.2 files
  4. 4. Run any database migrations if required (check Basercms documentation for upgrade commands)
  5. 5. Clear any cached data or temporary files
  6. 6. Verify the installation by logging into the admin panel
  7. 7. Test the Blog posts and Contents list features to confirm the XSS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Basercms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-46994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-46994 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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