CVE-2026-6953
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 · uneditedHTML injection vulnerability in Intermark IT's WebControl CMS v3.5. This vulnerability allows an attacker to send an email containing malicious HTML code to a victim via the contact form. To exploit this vulnerability, the attacker must send a request using the 'nombreApellidos', 'dirección ', and 'comentarios ' parameters to '/processContact.do'.
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 confidenceHTML injection vulnerability in WebControl CMS v3.5 contact form. The 'nombreApellidos', 'dirección', and 'comentarios' parameters on '/processContact.do' accept unsanitized HTML input that gets rendered in outgoing emails sent to the victim. An attacker can craft malicious HTML (including script tags, phishing forms, or malicious links) that executes when the recipient views the email.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Confirm WebControl CMS installation and versionLocate the CMS installation directory or check application metadata files for version information. Look for version identifiers in configuration files, about pages, or the main application banner.Affected if The installed version matches WebControl CMS v3.5 or falls within the v3.x release range.
-
Verify contact form endpoint is accessibleAttempt to access /processContact.do or locate the contact form in the web interface. Confirm the endpoint responds and accepts POST parameters.Affected if The contact form endpoint exists and is reachable, accepting input for 'nombreApellidos', 'dirección', or 'comentarios' parameters.
-
Confirm email functionality is enabledCheck CMS configuration settings for email/SMTP configuration. Verify that outgoing email is configured and functional.Affected if Email sending is enabled and the CMS processes form submissions by generating outgoing emails.
-
Inspect input handling on vulnerable parametersSubmit test input containing HTML characters (e.g., <script>alert(1)</script>) to the nombreApellidos, dirección, or comentarios fields. Examine the resulting outgoing email or email template to see if raw HTML is rendered.Affected if HTML or script tags submitted to these parameters appear unencoded or unescaped in the outgoing email content.
A user is affected if WebControl CMS v3.5 is installed, the contact form is active, and HTML submitted to the nombreApellidos, dirección, or comentarios parameters is rendered unescaped in outgoing emails.
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.
From vendor dataImplement robust input validation and output encoding on all three parameters before including them in email content. Use HTML entity encoding or a allowlist-based sanitizer to strip malicious HTML/script tags while preserving legitimate formatting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6953 — 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-6953 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