dbcve.org
Starsea MallApplication · Starsea99

CVE-2025-2352

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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, which was classified as problematic, has been found in StarSea99 starsea-mall 1.0. This issue affects some unknown processing of the file /admin/indexConfigs/save of the component Backend. The manipulation of the argument categoryName leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. Other parameters might be affected as well. The vendor was contacted early about this disclosure but did not respond in any way.

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 · high confidence

A stored cross-site scripting (XSS) vulnerability in starsea-mall 1.0 allows remote attackers to inject malicious JavaScript via the categoryName parameter in the /admin/indexConfigs/save endpoint. The vulnerable component is the Backend's configuration save function, where user-supplied input is not properly sanitized before storage and later rendering.

MitigationImplement strict input validation and context-aware output encoding for the categoryName parameter and all other user inputs in the affected endpoint. Use parameterized queries or an ORM to prevent stored XSS, and consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Starsea MallApplication
Affected:= 1.0.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 Starsea Mall installation
    Locate the application files or check the running web server for starsea-mall components. Look for the application's main directory structure or check the deployed web application name.
    Affected if The system is running Starsea99 Starsea Mall version 1.0.0
  2. Verify the application version
    Check the application's version information through the UI, configuration files, or API endpoints. Compare the installed version to the affected range (1.0.0).
    Affected if The installed version is exactly 1.0.0
  3. Check access to the admin endpoint
    Attempt to access the /admin/indexConfigs/save endpoint through HTTP request to determine if the backend configuration interface is exposed and accessible.
    Affected if The /admin/indexConfigs/save endpoint is accessible without proper authentication or with low-privilege admin access
  4. Inspect stored categoryName data
    Examine the application's database or configuration storage for any records in the indexConfigs table. Look for entries containing the categoryName field and check for unescaped HTML/JavaScript characters.
    Affected if The database contains categoryName values with raw HTML tags or JavaScript code that would execute when rendered

A user is affected if they are running Starsea Mall version 1.0.0 and the /admin/indexConfigs/save endpoint is accessible, as this allows injection of malicious JavaScript through the categoryName parameter that gets stored and rendered without sanitization.

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

Implement strict input validation and context-aware output encoding for the categoryName parameter and all other user inputs in the affected endpoint. Use parameterized queries or an ORM to prevent stored XSS, and consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

Fix this in Starsea Mall Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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