CVE-2025-10662
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 has been found in SeaCMS up to 13.3. The impacted element is an unknown function of the file /admin_members.php?ac=editsave. Such manipulation of the argument ID leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This affects another injection point than CVE-2025-25513.
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 confidenceSQL injection vulnerability in SeaCMS admin_members.php via the 'editsave' action allows remote attackers to inject malicious SQL queries through the 'ID' parameter. The flaw stems from unsanitized user input being directly used in database queries. With a CVSS 9.8 rating, this critical flaw can be exploited remotely without authentication to potentially extract, modify, or destroy database contents.
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<= 13.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SeaCMS installationSearch for SeaCMS files in the web root directory, typically looking for the characteristic admin_members.php file in the /admin/ folder or a /sea/ directory structureAffected if SeaCMS files are found on the system
-
Identify SeaCMS versionLocate the version file or check the version identifier in common SeaCMS locations such as the footer, /data/version.php, or the main index pageAffected if The installed version is 13.3 or any version lower than 13.3
-
Verify vulnerable file existsConfirm the presence of admin_members.php in the admin directory of the SeaCMS installationAffected if The file admin_members.php exists in the SeaCMS admin folder
-
Check admin panel accessibilityDetermine if the SeaCMS admin panel is accessible over the network by attempting to access the admin login page or checking server access logs for admin panel requestsAffected if The admin panel is reachable from the network without proper network restrictions
-
Review application exposureAssess whether the SeaCMS application is exposed directly to the internet or behind adequate network filteringAffected if The vulnerable admin panel is accessible from untrusted networks
A user is affected if SeaCMS version 13.3 or lower is installed, the admin_members.php file exists, and the admin panel is accessible either without authentication or with compromised credentials.
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 dataApply input validation and use parameterized queries/prepared statements for all database operations involving user-supplied data. If no patch is available, consider restricting access to the admin panel via network-level controls or Web Application Firewall rules until official remediation is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10662 — 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-10662 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