fkie_cve-2025-52921
Vulnerability from fkie_nvd
Published
2025-06-23 12:15
Modified
2025-06-23 20:16
Severity ?
9.9 (Critical) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
Summary
In Innoshop through 0.4.1, an authenticated attacker could exploit the File Manager functions in the admin panel to achieve code execution on the server, by uploading a crafted file and then renaming it to have a .php extension by using the Rename Function. This bypasses the initial check that uploaded files are image files. The application relies on frontend checks to restrict the administrator from changing the extension of uploaded files to .php. This restriction is easily bypassed with any proxy tool (e.g., BurpSuite). Once the attacker renames the file, and gives it the .php extension, a GET request can be used to trigger the execution of code on the server.
References
cve@mitre.orghttps://github.com/innocommerce/innoshop
cve@mitre.orghttps://medium.com/@The_Hiker/how-i-found-multiple-cves-in-innoshop-0-4-1-12c8f84ad87f
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In Innoshop through 0.4.1, an authenticated attacker could exploit the File Manager functions in the admin panel to achieve code execution on the server, by uploading a crafted file and then renaming it to have a .php extension by using the Rename Function. This bypasses the initial check that uploaded files are image files. The application relies on frontend checks to restrict the administrator from changing the extension of uploaded files to .php. This restriction is easily bypassed with any proxy tool (e.g., BurpSuite). Once the attacker renames the file, and gives it the .php extension, a GET request can be used to trigger the execution of code on the server."
    },
    {
      "lang": "es",
      "value": "En Innoshop hasta la versi\u00f3n 0.4.1, un atacante autenticado pod\u00eda explotar las funciones del Administrador de Archivos del panel de administraci\u00f3n para ejecutar c\u00f3digo en el servidor. Para ello, sub\u00eda un archivo manipulado y lo renombraba con la extensi\u00f3n .php mediante la funci\u00f3n Renombrar. Esto evita la comprobaci\u00f3n inicial de que los archivos subidos son im\u00e1genes. La aplicaci\u00f3n utiliza comprobaciones del frontend para impedir que el administrador cambie la extensi\u00f3n de los archivos subidos a .php. Esta restricci\u00f3n se puede eludir f\u00e1cilmente con cualquier herramienta proxy (p. ej., BurpSuite). Una vez que el atacante renombra el archivo y le asigna la extensi\u00f3n .php, se puede usar una solicitud GET para activar la ejecuci\u00f3n de c\u00f3digo en el servidor."
    }
  ],
  "id": "CVE-2025-52921",
  "lastModified": "2025-06-23T20:16:21.633",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "LOW",
          "baseScore": 9.9,
          "baseSeverity": "CRITICAL",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L",
          "version": "3.1"
        },
        "exploitabilityScore": 3.1,
        "impactScore": 6.0,
        "source": "cve@mitre.org",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-06-23T12:15:22.970",
  "references": [
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/innocommerce/innoshop"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://medium.com/@The_Hiker/how-i-found-multiple-cves-in-innoshop-0-4-1-12c8f84ad87f"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-420"
        }
      ],
      "source": "cve@mitre.org",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.