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

CVE-2026-42759

HIGH · 7.1 CVSS v3.1 Published 2026-05-27
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 Timo Affiliate Super Assistent amazonsimpleadmin allows Stored XSS.This issue affects Affiliate Super Assistent: from n/a through <= 1.10.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 · high confidence

A stored Cross-Site Scripting (XSS) vulnerability in Timo Affiliate Super Assistent (amazonsimpleadmin) allows authenticated attackers to inject malicious JavaScript scripts through unsanitized input fields. The malicious payload persists in the database and executes when other users view the affected pages, potentially leading to session hijacking or credential theft.

MitigationImplement proper input validation and output encoding/escaping for all user-supplied data. Sanitize existing stored data in the database to remove any injected payloads. Apply context-aware encoding when rendering data in HTML, JavaScript, or other contexts.

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 Timo Affiliate Super Assistent installation
    Search your web server file system for directories or files containing 'amazonsimpleadmin' or 'timo-affiliate'. Check for the plugin/admin panel accessible via your web application's /wp-admin/, /admin/, or similar paths.
    Affected if The software is present on the server or accessible as a plugin/module.
  2. Determine the installed version
    Look for version information in plugin metadata files (readme.txt, plugin.php header, composer.json, or VERSION files) within the amazonsimpleadmin directory. Check the admin dashboard plugins page if this is a WordPress plugin.
    Affected if The version cannot be determined or falls within any vulnerable range (consult CVE references for specific versions).
  3. Check for admin/affiliate input fields
    Navigate to the plugin admin interface and identify any input fields that accept user-supplied data for affiliate settings, commission configurations, or user profile fields. These are the potential injection points.
    Affected if Input fields that accept text and appear to lack output encoding are present in the admin panel.
  4. Inspect database for stored XSS payloads
    Query your database for common XSS patterns in tables related to the plugin, such as: <script, javascript:, onerror=, onload=, <img, <svg, and other HTML/script tags stored in affiliate-related fields.
    Affected if Malicious script tags or event handlers are found stored in the database.
  5. Review access logs for suspicious requests
    Examine web server access logs for POST requests to plugin admin pages containing XSS payloads in parameter values, especially if they originate from lower-privilege authenticated users.
    Affected if Logs show XSS payloads being submitted to affiliate configuration endpoints.

You are affected if Timo Affiliate Super Assistent is installed and any user-supplied data in its input fields can be rendered without sanitization to other users viewing the admin interface.

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 proper input validation and output encoding/escaping for all user-supplied data. Sanitize existing stored data in the database to remove any injected payloads. Apply context-aware encoding when rendering data in HTML, JavaScript, or other contexts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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