CVE-2020-24075
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 · uneditedCross Site Scripting (XSS) vulnerability in Name Input Field in Contact Us form in Laborator Kalium before 3.0.4, allows remote attackers to execute arbitrary code.
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 confidenceThis is a reflected Cross Site Scripting (XSS) vulnerability in the Laborator Kalium WordPress theme. The vulnerability exists in the Name input field of the Contact Us form, allowing remote attackers to inject malicious JavaScript code that executes when the form data is processed or displayed.
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< 3.0.4CVSS 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 Kalium theme versionLocate the theme's style.css file in wp-content/themes/kalium/ and read the Version header, or check the version displayed in WordPress admin under Appearance > Themes > Kalium.Affected if The version listed is below 3.0.4 (for example, 3.0.3, 3.0.2, etc.).
-
Confirm contact form is activeNavigate to your WordPress admin panel and check if the Kalium contact form is enabled, typically under Theme Options or a dedicated contact form settings page.Affected if The contact form functionality is enabled and publicly accessible.
-
Inspect contact form for missing sanitizationView the page containing the Contact Us form (usually at /contact or similar), view the page source, and check if the Name input field has any output encoding (look for proper HTML entity encoding of special characters like < > " ).Affected if The Name field outputs user input without encoding (you can test by submitting <script>alert(1)</script> and seeing if it executes).
-
Review server logs for XSS attemptsSearch your web server access logs for requests to the contact form endpoint that contain XSS payloads in the name parameter (search for patterns like <script, javascript:, onerror=, etc.).Affected if Logs show malicious scripts injected into the name parameter being processed by your server.
You are affected if the Kalium theme version is below 3.0.4 AND the contact form is enabled, allowing unauthenticated users to submit the Name field which then executes malicious JavaScript when viewed.
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 · scoped3.0.4
Upgrade to Laborator Kalium version 3.0.4 or later. As a temporary measure, implement server-side input validation and output encoding on the contact form fields to sanitize user-supplied data.
Kalium 3.0.4
- Log in to the WordPress admin dashboard
- Navigate to Appearance > Themes
- Locate the Kalium theme
- If a newer version (3.0.4 or later) is available in the WordPress theme repository or from your vendor, click Update
- Alternatively, upload and install Kalium version 3.0.4 or later from the theme package obtained from ThemeForest or Laborator's official source
- After updating, verify the Contact Us form is functioning correctly
- Clear any caching plugins if present
- Test the Name input field in the Contact Us form to confirm XSS is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24075 — 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-2020-24075 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