dbcve.org
Modern Image Gallery AppApplication · Remyandrade

CVE-2025-70457

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A Remote Code Execution (RCE) vulnerability exists in Sourcecodester Modern Image Gallery App v1.0 within the gallery/upload.php component. The application fails to properly validate uploaded file contents. Additionally, the application preserves the user-supplied file extension during the save process. This allows an unauthenticated attacker to upload arbitrary PHP code by spoofing the MIME type as an image, leading to full system compromise.

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 confidence

Modern Image Gallery App v1.0 contains an unauthenticated RCE vulnerability in gallery/upload.php where the application trusts client-supplied MIME types without validating actual file contents and preserves user-controlled file extensions. Attackers can upload PHP files disguised as images, leading to full system compromise.

MitigationImplement server-side content validation (magic byte checking) to verify actual file type, rename uploaded files with generated extensions, store uploads outside web root or disable script execution, and add authentication requirements for upload 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
Modern Image Gallery AppApplication
Affected:= 1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Modern Image Gallery App v1.0 installation
    Locate the application web root directory and identify if the Modern Image Gallery App files are present. Look for gallery/upload.php in the web directory structure.
    Affected if The application directory structure with gallery/upload.php exists on the server.
  2. Check if upload endpoint is publicly accessible
    Attempt to access the gallery/upload.php endpoint from an unauthenticated request (e.g., via curl or browser). Verify whether the upload form loads without requiring login credentials.
    Affected if The upload.php page loads or accepts requests without any authentication requirement.
  3. Inspect upload handling for MIME type validation
    Examine the gallery/upload.php source code to determine if server-side content validation (magic byte/file signature checking) is performed before accepting files. Look for functions that verify actual file contents versus trusting client-supplied Content-Type headers.
    Affected if The upload code does not perform server-side content validation and relies solely on client-provided MIME types.
  4. Verify file extension handling
    Review the upload code to see if user-controlled file extensions are preserved or if files are renamed with generated extensions. Check if uploaded files retain .php or other executable extensions.
    Affected if Uploaded files are saved with their original user-supplied extensions, allowing .php files to be stored directly.
  5. Confirm upload storage location is web-accessible
    Determine where uploaded files are stored (check upload directory configuration). Verify if the upload directory is within the web root and if PHP execution is allowed in that directory.
    Affected if Uploaded files are stored in a web-accessible directory where script execution is not disabled.

If Modern Image Gallery App v1.0 is installed with gallery/upload.php accessible without authentication, and the upload code lacks server-side content validation while preserving user-controlled file extensions in a web-accessible directory, the environment is vulnerable to CVE-2025-70457.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side content validation (magic byte checking) to verify actual file type, rename uploaded files with generated extensions, store uploads outside web root or disable script execution, and add authentication requirements for upload functionality.

Fix this in Modern Image Gallery App Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-70457 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-70457 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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