CVE-2024-25399
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 · uneditedSubrion CMS 4.2.1 is vulnerable to Cross Site Scripting (XSS) via adminer.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 confidenceSubrion CMS 4.2.1 contains a Cross Site Scripting (XSS) vulnerability in the adminer.php file. The vulnerability allows injection of malicious scripts through user-supplied input, likely due to insufficient input sanitization in the admin panel functionality.
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= 4.2.1CVSS 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.
-
Identify Subrion CMS installation and versionLocate the Subrion CMS installation directory and check the version number, typically found in a version file, composer.json, or in the admin dashboard under system information. Compare your installed version to the affected version 4.2.1.Affected if The installed version is exactly 4.2.1
-
Locate adminer.php fileSearch for the adminer.php file within the Subrion CMS installation directory structure. This file is part of the admin panel functionality.Affected if The adminer.php file exists in the installation
-
Verify admin panel accessibilityCheck whether the admin panel interface is accessible or enabled in the environment. XSS in adminer.php would require an attacker to access or inject into the admin panel context.Affected if The admin panel functionality is accessible or in use
-
Check input handling in adminer.phpIf you have access to the source code, inspect the adminer.php file for how user-supplied input is handled. Look for lack of input validation or output encoding on user-controllable parameters.Affected if The code in adminer.php processes user input without proper sanitization
You are affected if you are running Subrion CMS version 4.2.1 and the adminer.php file exists in your installation, as the XSS vulnerability exists in that specific file within that specific version.
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 proper input validation and output encoding for all user-supplied data in adminer.php. Use context-aware sanitization and consider Content Security Policy headers to mitigate XSS risks.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25399 — 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-25399 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