cvelist/2021/38xxx/CVE-2021-38346.json

{
    "CVE_data_meta": {
        "ASSIGNER": "security@wordfence.com",
        "DATE_PUBLIC": "2021-10-13T00:00:00.000Z",
        "ID": "CVE-2021-38346",
        "STATE": "PUBLIC",
        "TITLE": "Brizy <= 2.3.11 Authenticated Unrestricted File Upload and Path Traversal"
    },
    "affects": {
        "vendor": {
            "vendor_data": [
                {
                    "product": {
                        "product_data": [
                            {
                                "product_name": "Brizy - Page Builder",
                                "version": {
                                    "version_data": [
                                        {
                                            "platform": "WordPress",
                                            "version_affected": "<=",
                                            "version_name": "2.3.11",
                                            "version_value": "2.3.11"
                                        }
                                    ]
                                }
                            }
                        ]
                    },
                    "vendor_name": "Brizy.io"
                }
            ]
        }
    },
    "credit": [
        {
            "lang": "eng",
            "value": "Ramuel Gall, Wordfence"
        }
    ],
    "data_format": "MITRE",
    "data_type": "CVE",
    "data_version": "4.0",
    "description": {
        "description_data": [
            {
                "lang": "eng",
                "value": "The Brizy Page Builder plugin <= 2.3.11 for WordPress allowed authenticated users to upload executable files to a location of their choice using the brizy_create_block_screenshot AJAX action. The file would be named using the id parameter, which could be prepended with \"../\" to perform directory traversal, and the file contents were populated via the ibsf parameter, which would be base64-decoded and written to the file. While the plugin added a .jpg extension to all uploaded filenames, a double extension attack was still possible, e.g. a file named shell.php would be saved as shell.php.jpg, and would be executable on a number of common configurations."
            }
        ]
    },
    "generator": {
        "engine": "Vulnogram 0.0.9"
    },
    "impact": {
        "cvss": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 8.8,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
        }
    },
    "problemtype": {
        "problemtype_data": [
            {
                "description": [
                    {
                        "lang": "eng",
                        "value": "CWE-79 Cross-site Scripting (XSS)"
                    }
                ]
            }
        ]
    },
    "references": {
        "reference_data": [
            {
                "refsource": "MISC",
                "url": "https://www.wordfence.com/blog/2021/10/multiple-vulnerabilities-in-brizy-page-builder-plugin-allow-site-takeover/",
                "name": "https://www.wordfence.com/blog/2021/10/multiple-vulnerabilities-in-brizy-page-builder-plugin-allow-site-takeover/"
            }
        ]
    },
    "source": {
        "discovery": "INTERNAL"
    }
}