dbcve.org
CWE-259Weakness · CWE-259

CVE-2025-13252

HIGH · 7.3 CVSS v3.1 Published 2025-11-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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 shsuishang ShopSuite ModulithShop up to 45a99398cec3b7ad7ff9383694f0b53339f2d35a. Affected by this issue is some unknown functionality of the component RSA/OAuth2/Database. The manipulation results in hard-coded credentials. The attack can be executed remotely. The exploit has been made public and could be used. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable.

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

Hard-coded credentials vulnerability in ShopSuite ModulithShop's RSA/OAuth2/Database authentication component. Attackers can exploit publicly known credentials to authenticate remotely to the affected system.

MitigationIdentify and remove all hard-coded credentials from the codebase and replace with secure secret management (environment variables, vault, or secrets manager). Rotate any exposed credentials immediately.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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 ShopSuite ModulithShop installation
    Search for ShopSuite ModulithShop installation directories, running services, or application files on your system. Check common web server directories (e.g., /var/www, /opt, C:\inetpub) for ShopSuite-related folders.
    Affected if ShopSuite ModulithShop is found installed on the system
  2. Locate authentication configuration files
    Find configuration files related to RSA, OAuth2, or Database authentication in the ShopSuite installation directory. Look in config/, conf/, settings/, or similar directories for files containing auth, oauth, rsa, database, or credentials in their names.
    Affected if Authentication configuration files exist and are accessible
  3. Inspect for hard-coded credentials
    Open the identified authentication configuration files and search for hard-coded username/password pairs, API keys, tokens, or private keys. Look for fields like 'password', 'secret', 'key', 'token', 'credential' with visible values.
    Affected if Hard-coded credentials (usernames, passwords, keys, tokens) are present in authentication configuration files
  4. Verify authentication component is remotely accessible
    Check network configuration, firewall rules, or application settings to determine if the RSA/OAuth2/Database authentication endpoints are exposed to remote/network access. Look for listen addresses, allowed hosts, or network binding configurations.
    Affected if The authentication component is configured for remote/network access (not localhost-only)
  5. Compare installed version to affected product
    Determine the exact version of ShopSuite ModulithShop installed by checking version files, about pages, or application metadata. Compare against any available version information for this product.
    Affected if The installed version matches ShopSuite ModulithShop and the authentication component is in use

A user is affected if ShopSuite ModulithShop is installed with RSA, OAuth2, or Database authentication configured and hard-coded credentials are present in the authentication configuration files accessible remotely.

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

Identify and remove all hard-coded credentials from the codebase and replace with secure secret management (environment variables, vault, or secrets manager). Rotate any exposed credentials immediately.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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