CVE-2024-44683
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 · uneditedSeacms v13 is vulnerable to Cross Site Scripting (XSS) via admin-video.php.
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 confidenceSeacms v13 contains a cross-site scripting (XSS) vulnerability in the admin-video.php file. This allows attackers to inject malicious scripts that execute in the context of other users' browsers, potentially compromising admin sessions or stealing credentials.
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.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Seacms versionLocate the version file or index page of your Seacms installation and identify the installed version numberAffected if The installed version is exactly 13.0 (Seacms v13)
-
Locate admin-video.phpFind the admin-video.php file in your Seacms installation directory, typically under /admin/ or /include/ pathsAffected if The file admin-video.php exists in your Seacms installation
-
Verify admin panel accessibilityCheck if the Seacms admin interface is accessible by attempting to access the /admin/ directory or admin login pageAffected if The admin panel is exposed and reachable without additional authentication barriers
-
Inspect admin-video.php for unsanitized inputOpen admin-video.php in a text editor and search for any user-supplied parameters (GET, POST, or cookie values) that are output directly to HTML without sanitization functions like htmlspecialchars()Affected if The code in admin-video.php contains user input echoed directly to HTML output without proper encoding
-
Review request parameters for XSS vectorsSubmit test requests to admin-video.php with benign script tags in parameters and observe if they are reflected unescaped in the responseAffected if Parameters submitted to admin-video.php are reflected in the response without HTML encoding
You are affected if you are running Seacms version 13.0 and the admin-video.php file processes and outputs user input without sanitization.
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 input validation and proper output encoding on all user-supplied data in admin-video.php. Consider adding a Content Security Policy (CSP) header to mitigate XSS attacks.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-44683 — 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-2024-44683 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