dbcve.org
Natro MacroApplication · Natroteam

CVE-2026-28800

HIGH · 8.0 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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
Natro Macro is an open-source Bee Swarm Simulator macro written in AutoHotkey. Prior to version 1.1.0, anyone with Discord Remote Control set up in a non-private channel gives access to any user with the permission to send message in said channel access to do anything on their computer. This includes keyboard and mouse inputs and full file access. This issue has been patched in version 1.1.0.

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

Natro Macro prior to version 1.1.0 has a critical access control vulnerability in its Discord Remote Control feature. When configured in a non-private Discord channel, any user with message permissions in that channel can send commands that are executed on the victim's machine, allowing full keyboard/mouse control and file system access.

MitigationUpgrade to version 1.1.0 or later. Additionally, ensure Discord Remote Control is only configured in private channels with limited, trusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Natro MacroApplication
Affected:< 1.1.0

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed Natro Macro version
    Locate the Natro Macro installation directory and check the version information (typically via executable properties, an about dialog, or version file within the program folder). Compare the version number against the affected range (versions prior to 1.1.0).
    Affected if The installed version is Natro Macro and the version is below 1.1.0
  2. Confirm Discord Remote Control feature is enabled
    Examine Natro Macro's settings, configuration files, or preferences related to Discord integration. Look for any Discord Remote Control or similar feature that enables command execution via Discord messages.
    Affected if Discord Remote Control is enabled or configured in the application settings
  3. Inspect Discord channel visibility settings
    Review the Discord channel configuration where the Remote Control feature is connected. Determine whether the channel is set to private (only trusted members can access) or is a public/shared channel where any server member can view and send messages.
    Affected if The Remote Control is configured to use a public or shared Discord channel rather than a private, restricted channel

You are affected if Natro Macro version is below 1.1.0 AND the Discord Remote Control feature is enabled in a non-private Discord channel where untrusted users have message access.

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
Upgrade available Upgrade to 1.1.0 or later
Fixed in 1.1.0
Interim mitigation

Upgrade to version 1.1.0 or later. Additionally, ensure Discord Remote Control is only configured in private channels with limited, trusted users.

Recommended fix High confidence

1.1.0

  1. 1. Back up your current Natro Macro configuration files and settings.
  2. 2. Navigate to the official Natro Macro GitHub repository.
  3. 3. Locate and download version 1.1.0 or the latest stable release.
  4. 4. Uninstall or remove the existing Natro Macro installation.
  5. 5. Install the version 1.1.0 download.
  6. 6. Restore your backed-up configuration files if applicable.
  7. 7. Reconfigure Discord Remote Control settings, ensuring it is set up in a private channel rather than a public one.
  8. 8. Test the application to verify it functions correctly after the upgrade.
Caveat Minimal expected; this is a security patch release addressing unauthorized access via Discord Remote Control

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

Fix this in Natro Macro Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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