CVE-2025-65474
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 · uneditedAn arbitrary file rename vulnerability in the /admin/manager.php component of EasyImages 2.0 v2.8.6 and below allows attackers to execute arbitrary code via renaming a PHP file to a SVG format.
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 confidenceThe EasyImages 2.0 /admin/manager.php component contains an arbitrary file rename vulnerability allowing unauthenticated or low-privilege attackers to rename existing PHP files to .svg extension. Since SVG files can contain embedded malicious scripts or be executed in certain server configurations, this enables arbitrary code execution.
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<= 2.8.6CVSS 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.
-
Identify EasyImages versionLocate the EasyImages installation directory and check for version indicators such as a version.php file, a CHANGELOG, or the main script header comments that display the version number.Affected if The installed version is 2.8.6 or lower, or no version information is found (indicating an older unpatched release).
-
Verify vulnerable component existsLocate the /admin/manager.php file within the EasyImages installation directory.Affected if The file manager.php exists in the admin folder, indicating the vulnerable component is present.
-
Confirm admin access statusDetermine whether the /admin/ directory is accessible without authentication or if any authentication bypass exists. Attempt to access the manager.php component directly.Affected if The admin manager.php component can be accessed without valid authentication or the authentication can be bypassed, enabling the file rename functionality.
-
Check file rename configurationInspect the application configuration and manager.php code to determine if file rename operations allow changing file extensions to executable types like .php or .svg.Affected if File rename operations permit changing file extensions to .svg or other executable formats without strict validation, allowing code execution.
A user is affected if they are running EasyImages 2.0 version 2.8.6 or lower with the /admin/manager.php component accessible and the file rename functionality unrestricted to executable extensions.
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 allowlist-based file extension validation in the rename function, enforce proper authentication and authorization checks for the manager.php component, and restrict the rename operation to non-executable extensions.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65474 — 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-65474 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