dbcve.org
SeacmsApplication

CVE-2025-15002

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-21
Fix available
A fix is available. Upgrade to after 13.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 has been found in SeaCMS up to 13.3. The affected element is an unknown function of the file js/player/dmplayer/dmku/class/mysqli.class.php. Such manipulation of the argument page/limit leads to sql injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.

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

SQL injection vulnerability in SeaCMS up to version 13.3 in the file js/player/dmplayer/dmku/class/mysqli.class.php. The page and limit parameters are not properly sanitized, allowing remote attackers to inject malicious SQL queries.

MitigationUpgrade SeaCMS to a patched version if available. Alternatively, implement input validation and WAF rules to block SQL injection attempts on the affected parameters until a patch is applied.

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
SeacmsApplication
Affected:>= 13.0, <= 13.3

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
High
Integrity
High
Availability
High

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

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. Locate SeaCMS installation directory
    Search the web server document root for SeaCMS files, typically in directories like /var/www/html/, /home/*/public_html/, or C:\inetpub\wwwroot\. Look for the presence of admin.php or index.php with SeaCMS branding.
    Affected if SeaCMS is installed on the server
  2. Determine installed SeaCMS version
    Check the version file or source code. Common locations include a version.php file, or inspect the main index.php or admin/login.php for a version string. Alternatively, check the footer of the admin panel if accessible.
    Affected if The installed version is >= 13.0 and <= 13.3
  3. Verify vulnerable file exists
    Check if the file js/player/dmplayer/dmku/class/mysqli.class.php exists within the SeaCMS installation directory.
    Affected if The vulnerable file exists in the installation
  4. Check if mysqli database class is in use
    Examine the SeaCMS database configuration (typically in /include/config.php or /data/config.inc.php) to determine which database class is configured. Look for settings specifying 'mysqli' as the database type.
    Affected if SeaCMS is configured to use the mysqli database class (mysqli.class.php)
  5. Inspect affected parameters in code
    Review the mysqli.class.php file for the page and limit parameter handling. Look for direct usage of these GET/POST parameters in SQL queries without proper sanitization.
    Affected if The code contains vulnerable SQL queries using page or limit parameters without prepared statements or escaping

A user is affected if they run SeaCMS versions 13.0 through 13.3, have the mysqli.class.php file present, and the application uses the mysqli database driver with the vulnerable page/limit parameters accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 13.3
Interim mitigation

Upgrade SeaCMS to a patched version if available. Alternatively, implement input validation and WAF rules to block SQL injection attempts on the affected parameters until a patch is applied.

Recommended fix Moderate confidence

Latest stable SeaCMS release (verify with vendor for version beyond 13.3)

  1. 1. Contact SeaCMS official support or visit the official website to verify the availability of a patched version beyond 13.3
  2. 2. If a newer version is available, download it from the official SeaCMS source only
  3. 3. Before upgrading, perform a complete backup of the database and all website files
  4. 4. Test the new version in a staging environment to verify the SQL injection is resolved
  5. 5. Deploy the updated version to production after successful testing
  6. 6. As a temporary mitigation, review and restrict access to the affected endpoint (js/player/dmplayer/dmku/) using web server access controls or WAF rules until the upgrade is complete
Caveat Review release notes for any breaking changes between your current version and the target upgrade version before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seacms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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