dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-38669

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
wCMS v.1.4 is vulnerable to Cross Site Scripting (XSS) when creating a new blog.

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

wCMS v1.4 contains a stored Cross-Site Scripting (XSS) vulnerability in the blog creation functionality. Attackers can inject malicious JavaScript code into blog content fields that will be executed in the browsers of users who view the compromised blog post.

MitigationImplement robust input validation and output encoding/sanitization for all user-supplied content in the blog creation module to neutralize malicious script payloads.

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

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

  1. Identify wCMS installation and version
    Locate the wCMS installation directory and check for version indicators such as a version.php file, admin panel 'About' page, or footer/version metadata in the application.
    Affected if The installed version is wCMS v1.4 or if the version cannot be determined but the product is wCMS.
  2. Confirm blog module is enabled
    Check if the blog creation functionality is accessible by navigating to the blog creation page or checking the application's module configuration.
    Affected if The blog module is active and allows users to create or edit blog posts.
  3. Inspect blog content input handling
    Examine the server-side code that handles blog content submissions (typically in blog creation/editing controller or model files) for evidence of input validation or sanitization functions.
    Affected if The blog content input is stored and rendered without proper sanitization or output encoding.
  4. Check database for existing malicious content
    Query the database table storing blog posts (commonly 'posts', 'blog_posts', or similar naming) to inspect stored content for suspicious script tags or event handlers.
    Affected if The database contains blog entries with unencoded HTML or JavaScript payloads in content fields.

If wCMS v1.4 is running with the blog module enabled and no input sanitization is found in the blog creation code, the environment is likely affected by this stored XSS vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust input validation and output encoding/sanitization for all user-supplied content in the blog creation module to neutralize malicious script payloads.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-38669 — 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-2026-38669 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