CVE-2026-49774
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Filipe Nasc RD Station allows Remote Code Inclusion. This issue affects RD Station: from n/a through 5.6.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 · moderate confidenceA code injection vulnerability in RD Station (versions up to 5.6.0) allows remote code inclusion, enabling attackers to inject and execute arbitrary code on the affected system. The improper control of code generation allows unauthenticated attackers to potentially take complete control of the application.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify RD Station installationLocate the RD Station application and determine its installation method (on-premise, hosted, or SaaS). Check for version files, administrative panels, or package manifests that indicate the installed version.Affected if Cannot determine the version or version is 5.6.0 or lower
-
Verify installed versionAccess the RD Station administrative interface, version file, or API endpoint that reports the software version. Common locations include: /admin/about, config/settings files, or the help/about menu in the web interface.Affected if Installed version is 5.6.0 or any earlier version (e.g., 5.5.x, 5.4.x, etc.)
-
Inspect input handling modulesReview RD Station configuration files and code modules responsible for processing user inputs, particularly those that may accept code or script content. Look for settings related to custom code execution, webhooks, integrations, or dynamic content rendering.Affected if Code injection-capable modules are enabled and accessible to users
-
Check input validation configurationExamine the RD Station security or input validation settings. Look for configuration parameters controlling whether user-supplied data is validated, sanitized, or can be interpreted as executable code.Affected if Input validation is disabled, weak, or absent for the vulnerable code injection points
A system is affected if RD Station version is 5.6.0 or lower AND the vulnerable code injection feature/module is accessible and enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade RD Station to the latest version that addresses this vulnerability. If immediate patching is not possible, restrict network access to the application and implement input validation on all user-supplied data.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49774 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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