dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-7602

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-02
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 was found in JeecgBoot up to 3.9.1. Affected by this vulnerability is an unknown functionality of the file /sys/fillRule/edit of the component FillRuleUtil Component. The manipulation of the argument ruleClass results in improper authorization. The attack may be performed from remote. The exploit has been made public and could be used. You should upgrade the affected component. 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 JeecgBoot's FillRuleUtil component at the /sys/fillRule/edit endpoint. Attackers can manipulate the ruleClass argument to bypass authorization checks and access functionality they shouldn't have permission to use. The vulnerability is exploitable remotely and a public exploit exists.

MitigationUpgrade JeecgBoot to the version containing the vendor's fix when released. Until then, restrict network access to the /sys/fillRule/edit endpoint and monitor for unauthorized access attempts.

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 and version
    Locate the JeecgBoot application deployment (JAR, WAR, or compiled files) and check the version from the build artifacts, pom.xml, or application startup logs. Compare your installed version to the vendor's current release.
    Affected if The installed JeecgBoot version predates the vendor's fix for CVE-2026-7602.
  2. Verify FillRuleUtil component presence
    Search the deployed application for the FillRuleUtil class or related fill rule implementation files. This component handles the /sys/fillRule/edit endpoint functionality.
    Affected if The FillRuleUtil component is present and unpatched in the deployment.
  3. Confirm endpoint accessibility
    Check if the /sys/fillRule/edit endpoint is exposed in the application. Review the routing configuration or attempt a HEAD request to the endpoint (with appropriate authorization for testing only).
    Affected if The /sys/fillRule/edit endpoint is publicly or broadly accessible without proper network restrictions.
  4. Inspect authorization configuration
    Review the security or access control configuration for the fillRule endpoints. Check if ruleClass parameter validation and authorization checks are properly enforced on the /sys/fillRule/edit endpoint.
    Affected if Authorization controls are missing, misconfigured, or can be bypassed via ruleClass parameter manipulation.
  5. Review access logs for exploitation indicators
    Examine application access logs and security audit logs for suspicious requests to /sys/fillRule/edit that include unusual or unexpected ruleClass parameter values, especially from unauthorized users.
    Affected if Log analysis reveals unauthorized or anomalous fillRule edit requests that bypassed authorization.

A defender is affected if their JeecgBoot installation contains the vulnerable FillRuleUtil component, exposes the /sys/fillRule/edit endpoint, and lacks proper authorization controls on the ruleClass parameter - particularly if the version predates the vendor's fix.

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

Upgrade JeecgBoot to the version containing the vendor's fix when released. Until then, restrict network access to the /sys/fillRule/edit endpoint and monitor for unauthorized access attempts.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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