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

CVE-2026-32529

HIGH · 7.1 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in don-themes Molla molla allows Reflected XSS.This issue affects Molla: from n/a through < 1.5.19.

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

A reflected XSS vulnerability exists in the Molla theme where user-supplied input is not properly sanitized before being rendered in web pages. Attackers can inject malicious scripts through unsanitized parameters that get reflected back to users.

MitigationImplement proper input validation and output encoding/sanitization on all user-supplied parameters before rendering them in HTML context. Update to version 1.5.19 or later if available.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 if Molla theme is in use
    Search for molla theme files in the web root, check package.json for 'molla' or 'molla-theme' dependency, or look for theme-specific assets (CSS/JS files with 'molla' in the path)
    Affected if Molla theme files or dependencies are found in the environment
  2. Determine the installed Molla theme version
    Open the theme's package.json file (usually in the theme directory or at the project root) and locate the 'version' field, or check the theme header comment in main CSS/JS files
    Affected if The version field shows a version lower than 1.5.19 or no version is displayed (indicating an older release)
  3. Locate the parameter handling code
    Search the application source code for GET/POST parameter retrieval (e.g., $_GET, $_REQUEST, request.getParameter) and trace where these values are output to HTML templates or responses
    Affected if User-supplied parameters are being directly output to HTML without visible sanitization functions (such as htmlspecialchars, strip_tags, or encoding methods)
  4. Identify reflection points in templates
    Examine the theme's PHP, HTML, or template files for instances where request parameters are embedded into page output, particularly in search fields, URL parameters, or form values
    Affected if Parameters from requests are echoed back into the HTML output without encoding or sanitization applied at the template level

You are affected if the Molla theme is installed with a version earlier than 1.5.19 and your application reflects user-supplied URL or form parameters directly into HTML pages without sanitization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding/sanitization on all user-supplied parameters before rendering them in HTML context. Update to version 1.5.19 or later if available.

Recommended fix High confidence

Molla theme version 1.5.19 or later

  1. 1. Backup your current Molla theme installation and database before making any changes
  2. 2. Download Molla theme version 1.5.19 or later from the official don-themes source
  3. 3. Upload and install the new version through your WordPress theme upload or via FTP
  4. 4. Clear any caching mechanisms (page caches, CDN caches, server-side caches) after the upgrade
  5. 5. Verify the installation was successful by checking the theme version in your WordPress admin panel
  6. 6. Test the application to ensure all functionality works correctly post-upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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