Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-79571 – Unauthenticated Access Control Bypass – springboot-project v1.0.0 (Seller-Side)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-79571 is a critical incorrect access control vulnerability (CWE-284) affecting the SellerAuthorizeAspect component of the open-source springboot-project (v1.0.0), specifically its seller-side management module. The authorization aspect that is supposed to enforce authentication for seller management interfaces is non-functional, allowing unauthenticated attackers over the network to access and manipulate seller-side product, order, and category management functions. The issue carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: The SellerAuthorizeAspect class, an AOP (Aspect-Oriented Programming) component intended to intercept requests to seller management endpoints and verify authorization, has its authorization-check logic (the @Before/doVerify method and associated pointcut enforcement) effectively disabled/commented out, leaving the aspect with no active authorization logic.
  • Trigger conditions: Any unauthenticated network request to a seller-side management endpoint under the affected paths is processed as if it were authorized, because the AOP interceptor that should reject unauthenticated calls never executes its check.
  • Attack vector: Network (AV:N) — no authentication (PR:N) or user interaction (UI:N) is required; low attack complexity (AC:L).
  • Impact: Unauthenticated attackers can list all products and orders, change product sale status (e.g., toggle items on/off sale), complete or cancel orders, and edit product categories — resulting in high confidentiality and integrity impact (C:H/I:H). No direct availability impact was reported (A:N).

Affected software

  • springboot-project, seller-side management module — v1.0.0

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: No official patched version has been published in the CVE record or the public proof-of-concept writeup at the time of this analysis. Organizations running springboot-project v1.0.0 should treat all seller-side management endpoints (e.g., /seller/product/**, /seller/order/**, /seller/category/**) as unprotected until a fix is applied.
  • If no patch is available:
    • Re-enable and correctly implement the authorization-check logic inside the SellerAuthorizeAspect component (restore and fix the @Before/doVerify pointcut enforcement) before deploying to production.
    • Restrict network access to seller management interfaces using a firewall, reverse proxy, or API gateway so they are reachable only from trusted internal networks or authenticated management channels, not directly from the internet.
    • Monitor logs for unauthenticated calls to seller-side endpoints (product list/status, order operations, category edits) as an indicator of exploitation attempts.
    • Conduct a code review of any custom AOP-based authorization components before production deployment to confirm authorization logic is actually active and not left in a disabled/testing state.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge