dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-5999

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability has been found in JeecgBoot up to 3.9.1. This impacts an unknown function of the component SysAnnouncementController. Such manipulation leads to improper authorization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The vendor confirmed the issue and will provide a fix in the upcoming release.

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 confidence

Improper authorization vulnerability in SysAnnouncementController of JeecgBoot up to version 3.9.1 allows remote attackers to bypass access controls on announcement-related functionality, likely enabling unauthorized read, modify, or delete operations on system announcements.

MitigationApply vendor patch when released; until then, restrict network access to announcement endpoints, implement WAF rules to detect abnormal announcement API access patterns, and monitor for unauthorized announcement access in audit logs.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 JeecgBoot installation
    Locate the JeecgBoot application directory or JAR/WAR files. Check for jeecg-boot or jeecgboot in file paths, or look for the characteristic directory structure (resources, static, WEB-INF). On Linux, search with: find / -type d -name '*jeecg*' 2>/dev/null
    Affected if JeecgBoot is not installed in the environment (not affected)
  2. Determine JeecgBoot version
    Locate the version file or build descriptor. Check for version in pom.xml, application.yml/properties (jeecg.version property), or a VERSION/CHANGELOG file in the installation root. Compare the found version to the affected range: any version up to and including 3.9.1
    Affected if Version is 3.9.1 or lower (potentially affected)
  3. Verify SysAnnouncementController is deployed
    Inspect the deployed application WAR/JAR or decompiled classes. Look for SysAnnouncementController.class or SysAnnouncementController.java in the codebase. Check if the announcement module was included in the build
    Affected if SysAnnouncementController class exists in the deployment (potentially affected)
  4. Check announcement endpoint accessibility
    Identify announcement API endpoints (typically /api/announcement, /sys/announcement, or similar paths under /api or /sys controllers). Test unauthenticated or low-privilege access: curl -k -s -o /dev/null -w '%{http_code}' https://TARGET/api/announcement/list or similar endpoint
    Affected if Endpoints respond without proper authorization (vulnerable)
  5. Review authorization configuration
    Examine Spring Security or shiro config files (SecurityConfig.java, ShiroConfig.java) for rules governing announcement routes. Check if announcement endpoints have role-based or method-level security annotations (@PreAuthorize, @Secured) properly configured
    Affected if No role-based restrictions or missing @PreAuthorize on announcement controller methods (potentially vulnerable)

If JeecgBoot version 3.9.1 or lower is confirmed AND the SysAnnouncementController is deployed AND announcement endpoints respond without proper authorization, the environment is affected by CVE-2026-5999.

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

Apply vendor patch when released; until then, restrict network access to announcement endpoints, implement WAF rules to detect abnormal announcement API access patterns, and monitor for unauthorized announcement access in audit logs.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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