Skip to main content
Vulnerability Database/CVE-2026-108617

CVE-2026-108617: JeecgBoot Authorization Bypass Vulnerability

CVE-2026-108617 is an authorization bypass flaw in JeecgBoot through version 3.9.5 allowing low-privileged users to create unauthorized message templates. This post covers technical details, affected versions, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-108617 Overview

CVE-2026-108617 is a missing authorization vulnerability [CWE-862] in JeecgBoot through version 3.9.5. The flaw resides in the POST /sys/message/sysMessageTemplate/add endpoint, which fails to verify that the caller holds the privileges required to create notification templates. Any authenticated user with minimal roles can insert arbitrary records into the shared sys_sms_template library used across system, email, SMS, and instant messaging notifications. Attackers can define template codes and content that downstream workflows later render to recipients, enabling template poisoning across every notification channel JeecgBoot drives.

Critical Impact

Low-privileged authenticated users can inject arbitrary notification templates into the shared messaging library, affecting system, email, SMS, and IM channels.

Affected Products

  • JeecgBoot versions up to and including 3.9.5
  • jeecg-module-system component, specifically SysMessageTemplateController
  • Deployments relying on sys_sms_template for notification delivery

Discovery Timeline

  • 2026-10-10 - CVE-2026-108617 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-108617

Vulnerability Analysis

The vulnerability is a classic missing authorization check. The add handler in SysMessageTemplateController accepts authenticated requests but does not enforce role-based authorization before writing new records to the message template store. Any session that passes authentication, regardless of assigned role, can submit a template definition and persist it. The impact is scoped to integrity of the template library; confidentiality and availability of the host system are not directly affected, which aligns with the limited integrity-only CVSS profile.

The shared template store is consumed by multiple downstream notification pipelines. Once poisoned, attacker-controlled template codes and bodies can be referenced by subsequent legitimate notification flows, producing attacker-chosen content to end users through trusted channels.

Root Cause

The root cause is the absence of an authorization annotation or programmatic permission check on the controller method handling template creation. The endpoint relies solely on authentication, treating any logged-in principal as entitled to administrative template management operations. See the GitHub Code Reference for the vulnerable method.

Attack Vector

An attacker obtains any valid low-privileged account on a target JeecgBoot instance. The attacker then issues an HTTP POST to /sys/message/sysMessageTemplate/add with a crafted JSON body containing a template code, name, type, and content. The server persists the record without an authorization check. The injected template is now available to any workflow that resolves notifications by template code. A public proof of concept is available at the GitHub PoC Repository and documented in the VulnCheck Security Advisory.

No verified sanitized exploitation code is republished here. Review the referenced proof of concept for request structure details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-108617

Indicators of Compromise

  • Unexpected INSERT operations on the sys_sms_template table performed by non-administrative accounts.
  • HTTP POST requests to /sys/message/sysMessageTemplate/add originating from accounts without template management responsibilities.
  • New records in sys_sms_template with template codes or content that do not match the organization's naming conventions or change management records.

Detection Strategies

  • Instrument application access logs to flag calls to /sys/message/sysMessageTemplate/add and correlate the authenticated user ID against the authorized template administrator list.
  • Add database audit rules that capture inserts into sys_sms_template and alert when the executing application user does not match an approved identity.
  • Baseline the expected rate of template creation and alert on deviations, since legitimate template authoring is typically infrequent.

Monitoring Recommendations

  • Forward JeecgBoot application and database audit logs to a central analytics platform for correlation across sessions and template objects.
  • Track outbound notification volumes by template code and alert when a newly created template drives unexpected traffic.
  • Monitor authentication telemetry for low-privileged accounts that suddenly interact with administrative endpoints.

How to Mitigate CVE-2026-108617

Immediate Actions Required

  • Restrict network access to the /sys/message/ administrative endpoints at the reverse proxy or web application firewall layer, limiting them to trusted administrative networks.
  • Audit the sys_sms_template table for templates created by non-administrative accounts and remove unauthorized entries.
  • Rotate credentials for any low-privileged accounts whose scope could reach the vulnerable endpoint while awaiting a vendor fix.

Patch Information

At the time of publication, no fixed version is identified in the NVD record for JeecgBoot. Track the VulnCheck Security Advisory and the upstream JeecgBoot repository for an authorization fix on SysMessageTemplateController#add and upgrade once a patched release is published.

Workarounds

  • Apply a reverse proxy rule that blocks requests to /sys/message/sysMessageTemplate/add from any identity not present in an allow list of template administrators.
  • Introduce a server-side authorization filter or Spring Security rule that requires an administrative role on all /sys/message/sysMessageTemplate/** write operations.
  • Enable database-level triggers that reject inserts into sys_sms_template outside of a change management window.
bash
# Example NGINX location block restricting the vulnerable endpoint
location = /sys/message/sysMessageTemplate/add {
    allow 10.0.0.0/24;   # administrative subnet
    deny all;
    proxy_pass http://jeecgboot_upstream;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.