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

CVE-2026-25033

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 uixthemes Motta Addons motta-addons allows Reflected XSS.This issue affects Motta Addons: from n/a through < 1.6.1.

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

Reflected Cross-site Scripting (XSS) vulnerability in Motta Addons plugin allows attackers to inject malicious JavaScript code through unsanitized user input that gets reflected in web pages without proper encoding.

MitigationUpgrade Motta Addons to version 1.6.1 or later. Until then, implement output encoding and input validation on affected endpoints, and advise users not to click untrusted links.

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. Check Motta Addons plugin version
    In WordPress admin, navigate to Plugins > Installed Plugins > Motta Addons and record the version number shown
    Affected if Installed version is lower than 1.6.1
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that Motta Addons shows as Active
    Affected if Plugin is active and version is below 1.6.1
  3. Identify vulnerable input points
    Since this is reflected XSS via unsanitized user input, review any publicly accessible pages that reflect URL parameters or user-supplied data without encoding. Common targets include search parameters, form submissions, or query strings
    Affected if Pages reflect URL parameters without proper encoding and plugin version is below 1.6.1

Environment is affected if Motta Addons plugin version is below 1.6.1 and user input is reflected without encoding on active pages

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

Upgrade Motta Addons to version 1.6.1 or later. Until then, implement output encoding and input validation on affected endpoints, and advise users not to click untrusted links.

Recommended fix Moderate confidence

Motta Addons version 1.6.1 or later

  1. Backup your WordPress site before making any changes
  2. Update Motta Addons to version 1.6.1 or later via the WordPress plugin admin panel, or upload the new version via FTP/SFTP by replacing the plugin files in wp-content/plugins/motta-addons/

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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