dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-58048

CRITICAL · 9.9 CVSS v3.1 Published 2025-08-28
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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
Paymenter is a free and open-source webshop solution for hostings. Prior to version 1.2.11, the ticket attachments functionality in Paymenter allows a malicious authenticated user to upload arbitrary files. This could result in sensitive data extraction from the database, credentials being read from configuration files, and arbitrary system commands being run under the web server user context. This vulnerability was patched by commit 87c3db4 and was released under the version 1.2.11 tag without any other code modifications compared to version 1.2.10. If upgrading is not immediately possible, administrators can mitigate this vulnerability with one or more of the following measures: updating nginx config to download attachments instead of executing them or disallowing access to /storage/ fully using a WAF such as Cloudflare.

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

Paymenter versions before 1.2.11 contain a file upload vulnerability in the ticket attachments feature that allows any authenticated user to upload arbitrary files, including executable scripts. This can lead to remote code execution, credential theft, and database data exfiltration.

MitigationUpgrade to version 1.2.11 immediately. If immediate upgrade is not feasible, configure nginx to prevent execution of files in /storage/ or deploy a WAF rule to block access to /storage/.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify if Paymenter is installed
    Locate the Paymenter installation directory or check for paymenter-related files/processes on the system. Look for the main application files or check running web services.
    Affected if Paymenter software is present on the system
  2. Determine the installed Paymenter version
    Check the version file or configuration within the Paymenter installation. Common locations include a version.php, composer.json, or the admin dashboard version display.
    Affected if The installed version is before 1.2.11 (e.g., 1.2.10, 1.2.9, or older)
  3. Verify if the ticket attachments feature is enabled
    Access the Paymenter admin panel, navigate to ticket settings or the attachments configuration area, and check whether file uploads for tickets are permitted.
    Affected if Ticket attachments feature is enabled and allows file uploads
  4. Check if /storage/ directory permits script execution
    Examine the web server configuration (nginx/apache) and the /storage/ directory structure to determine if uploaded files can be executed. Look for AllowOverride settings and directory execution permissions.
    Affected if The /storage/ directory is web-accessible and allows execution of uploaded files (e.g., .php, .exe, .sh scripts)

If Paymenter is installed with a version before 1.2.11 and the ticket attachments feature is enabled, the system is affected by this vulnerability.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to version 1.2.11 immediately. If immediate upgrade is not feasible, configure nginx to prevent execution of files in /storage/ or deploy a WAF rule to block access to /storage/.

Recommended fix High confidence

version 1.2.11

  1. Backup the current Paymenter installation and database before proceeding with the update
  2. Update Paymenter to version 1.2.11 (the version containing commit 87c3db4 that patches this vulnerability)
  3. Verify the update was successful by checking the application version
  4. If upgrade is not immediately possible, configure nginx to serve files from /storage/ as attachments rather than allowing execution (e.g., add 'Content-Disposition: attachment' header)
  5. Alternatively, configure a WAF rule (such as Cloudflare) to block all execution requests to the /storage/ directory

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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