CVE-2025-13246
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 · uneditedA vulnerability was identified in shsuishang ShopSuite ModulithShop up to 45a99398cec3b7ad7ff9383694f0b53339f2d35a. Impacted is the function JwtAuthenticationFilter of the file src/main/java/com/suisung/shopsuite/common/security/JwtAuthenticationFilter.java. The manipulation leads to path traversal. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.
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 confidenceA path traversal vulnerability exists in the JwtAuthenticationFilter component of ShopSuite ModulithShop, allowing remote attackers to potentially access files outside the intended directory through manipulation of file paths processed by this authentication filter.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify ShopSuite ModulithShop installationLocate the ShopSuite application files, JARs, WARs, or service installation directory on the system. Check common application server directories or deployment locations.Affected if ShopSuite ModulithShop is not found on the system
-
Determine installed versionCheck the application version by examining manifest files, version properties files, or the application startup logs. Look for version information in the deployment descriptor or configuration files.Affected if The installed version cannot be determined or is unknown
-
Verify JwtAuthenticationFilter is in useExamine the application's configuration files, web.xml, or Spring configuration for the presence of JwtAuthenticationFilter class. Check if JWT-based authentication is enabled in the security configuration.Affected if JwtAuthenticationFilter is not configured or not in use
-
Check for file path processing in authenticationReview the application's authentication flow and any code that handles file paths within or adjacent to the JwtAuthenticationFilter. Look for file upload, file serving, or file reference functionality integrated with authentication.Affected if File paths are processed through JwtAuthenticationFilter or related authentication components
-
Review access logs for path traversal attemptsExamine web server or application logs for unusual request patterns with ../ sequences, absolute path references, or encoded path characters that may indicate exploitation attempts.Affected if Suspicious path traversal patterns are found in access logs related to authenticated endpoints
A user is affected if ShopSuite ModulithShop is installed with JwtAuthenticationFilter processing file paths and the installed version falls within the affected version range (if known), particularly if path traversal patterns appear in authentication-related access logs.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict path validation and sanitization in JwtAuthenticationFilter to ensure all file paths remain within intended boundaries; restrict file access to approved directories only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13246 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13246 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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