dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-4305

MEDIUM · 6.3 CVSS v3.1 Published 2025-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 vulnerability has been found in kefaming mayi up to 1.3.9 and classified as critical. This vulnerability affects the function Upload of the file app/tools/controller/File.php. The manipulation of the argument File leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

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

The kefaming mayi application up to version 1.3.9 contains an unrestricted file upload vulnerability in the Upload function of app/tools/controller/File.php. The File parameter is not properly validated, allowing remote attackers to upload arbitrary files including executable scripts to the server.

MitigationImplement strict whitelist-based file validation including extension checking, MIME type verification, and file content analysis. Store uploaded files outside the web root or apply proper access controls to prevent execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Identify if kefaming mayi application is installed
    Search for the application by looking for the directory structure or files containing 'kefaming' or 'mayi' in the web root, or check for the specific file path app/tools/controller/File.php
    Affected if The application directory or the specific file app/tools/controller/File.php exists on the server
  2. Determine the installed version
    Check version files, composer.json, or any version indicator within the application root directory. Compare the found version to the affected range (1.3.9 and earlier)
    Affected if The installed version is 1.3.9 or any earlier version of kefaming mayi
  3. Verify the Upload function is accessible
    Check if the endpoint for the File controller's Upload function is accessible via HTTP/HTTPS. This typically involves accessing a URL path like /index.php/tools/file/upload or similar routing to app/tools/controller/File.php
    Affected if The Upload function in app/tools/controller/File.php is reachable via web request and accepts file uploads
  4. Check file upload configuration
    Inspect the application configuration or the File.php controller to determine if file upload functionality is enabled and whether there is any validation on the File parameter
    Affected if File uploads are allowed without proper validation on the File parameter, allowing arbitrary file types to be processed
  5. Determine uploaded file storage location
    Examine the application configuration or the File.php code to identify where uploaded files are stored. Check if files are saved within the web root in a publicly accessible directory
    Affected if Uploaded files are stored in web-accessible directories where they can be executed directly via browser access

A user is affected if they are running kefaming mayi version 1.3.9 or earlier, have the application accessible over the network, and the Upload function in app/tools/controller/File.php is exposed and processes file uploads without proper validation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict whitelist-based file validation including extension checking, MIME type verification, and file content analysis. Store uploaded files outside the web root or apply proper access controls to prevent execution.

Recommended fix Moderate confidence

latest stable version of kefaming mayi (version higher than 1.3.9)

  1. 1. Identify the currently running version of kefaming mayi by checking the application configuration or admin panel
  2. 2. Backup the entire application and database before making any changes
  3. 3. Download the latest stable release of kefaming mayi from the official repository or vendor
  4. 4. Replace the existing application files with the new version, preserving configuration files
  5. 5. Verify the file app/tools/controller/File.php has been updated in the new version
  6. 6. Test file upload functionality to ensure legitimate uploads still work
  7. 7. Confirm the vulnerability is no longer present by verifying proper file type/size validation is in place
Caveat review release notes for any breaking changes between your current version and the new version, particularly around file handling functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4305 — 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-4305 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