dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-5131

MEDIUM · 6.9 CVSS v4.0 Published 2026-04-17
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 Zero-click

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
GREENmod uses named pipes for communication between plugins, the web portal, and the system service, but the access control lists for these pipes are configured incorrectly. This allows an attacker to communicate with the stream and upload any XML or JSON file, which will be processed by the named pipe with the privileges of the user under whose context the service is running. This allows for Server-Side Request Forgery to any Windows system on which the agent is installed and which provides communication via SMB or WebDav. This issue was fixed in version 2.8.33.

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

GREENmod misconfigures Access Control Lists on named pipes used for communication between plugins, web portal, and the system service. This allows unauthenticated attackers to inject XML or JSON files that get processed with the service account's privileges, enabling Server-Side Request Forgery (SSRF) to internal Windows systems via SMB or WebDAV.

MitigationUpdate GREENmod to version 2.8.33 or later to patch the named pipe ACL misconfiguration. If immediate patching is not possible, restrict network access to the service and monitor for suspicious SMB/WebDAV activity.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 GREENmod is installed
    Check the installed version of GREENmod on the system using your system's package manager, installed programs list, or by querying the GREENmod service for its version information
    Affected if GREENmod is present and the version is below 2.8.33
  2. Verify the named pipe ACL configuration
    Use Windows ACL tools (such as icacls or PowerShell Get-Acl) to inspect the Access Control Lists on named pipes used by GREENmod for inter-process communication. Look for overly permissive settings that allow unauthenticated users write or full control access
    Affected if The named pipes have ACLs that permit unauthenticated or low-privilege users to write files to the pipe communication directories
  3. Confirm the service account context
    Check the Windows service configuration for GREENmod to identify the account under which the system service runs (typically visible via services.msc or sc queryex)
    Affected if The GREENmod service runs under a privileged account (such as SYSTEM, LocalSystem, or a domain admin account)
  4. Assess network exposure
    Determine whether the GREENmod web portal or plugin interfaces are accessible from untrusted networks or allow unauthenticated access
    Affected if The GREENmod interface is exposed to untrusted networks or permits unauthenticated file injection via XML or JSON uploads

A user is affected if GREENmod is installed with a version below 2.8.33, the named pipe ACLs permit unauthorized write access, and the service or web interface is accessible to unauthenticated attackers who could inject malicious XML/JSON files for SSRF exploitation.

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

Update GREENmod to version 2.8.33 or later to patch the named pipe ACL misconfiguration. If immediate patching is not possible, restrict network access to the service and monitor for suspicious SMB/WebDAV activity.

Recommended fix High confidence

Version 2.8.33

  1. Identify all systems running GREENmod that need to be patched
  2. Check the current installed version of GREENmod (versions prior to 2.8.33 are affected)
  3. Obtain the fixed version 2.8.33 from the official vendor source
  4. Create a full backup of the GREENmod configuration and data
  5. Test the upgrade in a non-production environment first to verify compatibility
  6. Apply the upgrade to production systems
  7. Verify the fix is successful and the SSRF vulnerability is resolved
  8. Confirm named pipe ACLs are correctly configured post-upgrade
Caveat Test thoroughly in non-production before deploying to production as a standard precaution

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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