CVE-2022-28525
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 · uneditedED01-CMS v20180505 was discovered to contain an arbitrary file upload vulnerability via /admin/users.php?source=edit_user&id=1.
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 confidenceED01-CMS v20180505 contains an arbitrary file upload vulnerability in the admin panel at /admin/users.php?source=edit_user&id=1. An authenticated attacker with admin privileges can upload malicious files, potentially achieving remote code execution on the server.
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= 20180505CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify installed ED01-CMS versionCheck the source code, changelog, or admin panel for the CMS version number. Common locations include a version.php file, footer in admin panel, or a readme.txt file in the web root.Affected if The installed version matches 20180505 exactly.
-
Verify vulnerable endpoint existsAccess the URL path /admin/users.php?source=edit_user&id=1 on the web server using a browser or curl request. Check if the page loads and presents an edit user form.Affected if The endpoint responds with HTTP 200 and displays an edit user form with file upload capability.
-
Confirm admin authentication statusAttempt to access the /admin/ directory. Check if authentication is required and whether default admin credentials (admin/admin, admin/password) or previously set admin accounts are valid.Affected if An authenticated session with admin privileges can be established.
-
Inspect file upload form parametersSubmit a GET request to the vulnerable URL and examine the HTML form for file input fields. Look for the enctype='multipart/form-data' attribute and any client-side file type restrictions.Affected if The form contains an unrestricted file input field allowing any file type to be selected for upload.
-
Check upload directory script executionIf uploads are present, locate the upload directory (typically /uploads/ or /admin/uploads/) and verify if .htaccess or server configuration allows script execution for uploaded files.Affected if Uploaded files with .php, .phtml, or other executable extensions can be executed by the web server.
A system is affected if it runs ED01-CMS version 20180505 with the admin panel accessible and the file upload feature present on the edit_user page without proper server-side validation.
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 strict server-side file type validation (allowlist approach), verify file magic bytes, rename uploaded files, and disable script execution in the upload directory.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28525 — 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-2022-28525 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