CVE-2024-46998
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 Edit Email Form Settings Feature. Version 5.1.2 fixes the 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 Edit Email Form Settings Feature. The vulnerability allows attackers to inject malicious scripts through unsanitized input fields in the email form settings, which then execute 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.
-
Check baserCMS installed versionLocate the baserCMS version number in the admin dashboard (typically under System or About section) or check the version file in the baserCMS installation directoryAffected if The installed version is any version prior to 5.1.2 (e.g., 5.1.1, 5.1.0, 5.0.x, etc.)
-
Verify Edit Email Form Settings Feature accessLog into the baserCMS admin panel and navigate to the Email Form Settings section (usually under Mail or Content management settings)Affected if The Edit Email Form Settings Feature is accessible and the baserCMS version is below 5.1.2
-
Confirm input fields accept unsanitized contentIf you have admin access, attempt to input HTML or script tags (e.g., <script>alert('test')</script>) into email form setting fields such as subject line, sender name, or message templatesAffected if The input fields accept and display unsanitized HTML or script content without encoding or sanitization
You are affected if your baserCMS installation is any version prior to 5.1.2 AND the Edit Email Form Settings Feature is enabled and accessible in your environment.
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 security fix. As a temporary measure, disable the Edit Email Form Settings Feature if possible until the upgrade can be performed.
5.1.2
- Backup the current BaserCMS installation and database before proceeding with any upgrade
- Download BaserCMS version 5.1.2 from the official basercms.net website or verified repository
- Follow the official BaserCMS upgrade documentation for your current version to update to 5.1.2
- After upgrade, verify that the Edit Email Form Settings feature no longer contains the XSS vulnerability
- Test the application functionality to ensure the upgrade did not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46998 — 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-46998 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