DATABASE RESOURCES PRICING ABOUT US

{"id": "SSV:99161", "type": "seebug", "bulletinFamily": "exploit", "title": "MyBB SQL\u6ce8\u5165\u6f0f\u6d1e\uff08CVE-2021-27946\uff09", "description": "", "published": "2021-03-19T00:00:00", "modified": "2021-03-19T00:00:00", "cvss": {"score": 6.5, "vector": "AV:N/AC:L/Au:S/C:P/I:P/A:P"}, "href": "https://www.seebug.org/vuldb/ssvid-99161", "reporter": "Knownsec", "references": [], "cvelist": ["CVE-2021-27946"], "immutableFields": [], "lastseen": "2021-07-24T16:05:09", "viewCount": 4, "enchantments": {"dependencies": {"references": [{"type": "cve", "idList": ["CVE-2021-27946"]}, {"type": "exploitdb", "idList": ["EDB-ID:49699"]}, {"type": "packetstorm", "idList": ["PACKETSTORM:161918"]}, {"type": "thn", "idList": ["THN:3152B45B015211515D21C5C8A05763F5"]}, {"type": "zdt", "idList": ["1337DAY-ID-36010"]}], "rev": 4}, "score": {"value": 4.5, "vector": "NONE"}, "backreferences": {"references": [{"type": "cve", "idList": ["CVE-2021-27946"]}, {"type": "exploitdb", "idList": ["EDB-ID:49699"]}, {"type": "packetstorm", "idList": ["PACKETSTORM:161918"]}, {"type": "thn", "idList": ["THN:3152B45B015211515D21C5C8A05763F5"]}, {"type": "zdt", "idList": ["1337DAY-ID-36010"]}]}, "exploitation": null, "vulnersScore": 4.5}, "sourceHref": "", "sourceData": "", "status": "cve", "cvss2": {}, "cvss3": {}, "_state": {"dependencies": 1646015791}}

{"cve": [{"lastseen": "2022-03-23T16:18:49", "description": "SQL Injection vulnerability in MyBB before 1.8.26 via poll vote count. (issue 1 of 3).", "cvss3": {"exploitabilityScore": 2.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "baseScore": 8.8, "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "version": "3.1", "userInteraction": "NONE"}, "impactScore": 5.9}, "published": "2021-03-15T18:15:00", "type": "cve", "title": "CVE-2021-27946", "cwe": ["CWE-89"], "bulletinFamily": "NVD", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 8.0, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "PARTIAL", "availabilityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "baseScore": 6.5, "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P", "version": "2.0", "accessVector": "NETWORK", "authentication": "SINGLE"}, "impactScore": 6.4, "acInsufInfo": false, "obtainUserPrivilege": false}, "cvelist": ["CVE-2021-27946"], "modified": "2021-03-23T22:14:00", "cpe": [], "id": "CVE-2021-27946", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27946", "cvss": {"score": 6.5, "vector": "AV:N/AC:L/Au:S/C:P/I:P/A:P"}, "cpe23": []}], "packetstorm": [{"lastseen": "2021-03-23T16:46:47", "description": "", "published": "2021-03-23T00:00:00", "type": "packetstorm", "title": "MyBB 1.8.25 SQL Injection", "bulletinFamily": "exploit", "cvelist": ["CVE-2021-27889", "CVE-2021-27946"], "modified": "2021-03-23T00:00:00", "id": "PACKETSTORM:161918", "href": "https://packetstormsecurity.com/files/161918/MyBB-1.8.25-SQL-Injection.html", "sourceData": "`# Exploit Title: MyBB 1.8.25 - Poll Vote Count SQL Injection \n# Exploit Author: SivertPL (kroppoloe@protonmail.ch) \n# Date: 20.03.2021 \n# Description: Lack of sanitization in the \"votes[]\" parameter in \"Edit Poll\" causes a second-order semi-blind SQL Injection that is triggered when performing a \"Move/Copy\" operation on the thread. \n# Sofware Link: https://resources.mybb.com/downloads/mybb_1825.zip \n# CVE: CVE-2021-27946 \n \nReferences: \n \n1) https://portswigger.net/daily-swig/chained-vulnerabilities-used-to-take-control-of-mybb-forums \n2) https://vuldb.com/?id.171307 \n3) https://github.com/mybb/mybb/commit/aa415f08bce01f95a8319b707bb18eb67833f4c1.patch \n \nIn order to trigger the vulnerability, you must have permission to edit polls. \nModerators and administrators can usually do it, but in some configurations regular users can do it as well. \n \nIn case you are a moderator, the vulnerability can be used as privilege escalation provided you crack the resulting salted hash. \n \nOtherwise, you are free to use CVE-2021-27889 to impersonate the target moderator to trigger this SQL Injection from an external .js script which will perform the necessary \ninjections automatically, and send the resulting hashes to your server. \n \nThis is a pretty nasty vulnerability to exploit by hand (at least on regular, most common MySQL setup), but can be dangerous in the hands of \na very determined attacker who combines it with CVE-2021-27889 and an automated Javascript-Based SQL Injector. \n \nThis vulnerability might however allow for devastating execution of stacked queries when databases such as PostgreSQL or MS-SQL are used. \nIn such cases, the entire system is compromised as a result (an attacker can UPDATE the admin password and replace it with his own hash). \n \nGuide: \n \n1) Make a thread with a public poll, with multiple choices. \n \n2) Vote on at least one choice. \n \n3) Go to the \"Edit poll\" section of the poll. \n \n4) Place the following payload in the \"vote count\" input (any entry within the votes[] parameter in the resulting POST request). \n \n1','2',ascii((select version())),'0','0','1','1') -- -a \n \n5) Save the poll. \n \n6) Perform a \"Move/Copy\" operation on the thread, moving it to a different forum, or making a copy in the same forum. \n \nThis is where the SQL Injection is triggered, and you should see an SQL Error here if the payload is incorrect. \n \n7) Go to the copied/moved version of the thread (you should be redirected there automatically). \n \n8) Go to the \"Show Results\" section of the poll. \n \n9) The total vote count under the poll is our 64 bit unsigned integer covert channel to retrieve information from the ascii select query. \n \nSince this vulnerability is semi-blind, you can only retrieve the output of the SELECT query as an unsigned integer (hence we use ASCII()). \nOther parameters in the INSERT query that we are injecting into are either too small, or unfeasible. \nUnsigned integer provides enough space to extract required data when enough requests are made. \n \nIn this case, the number is the ASCII code of the first character of the result of the injected select version() query. \nThis way we can transfer the output through this covert channel, one character at a time. \n \nIn order to extract the admin hash, one has to either perform many requests (so it's best to automate it), or find a better way to convert a substring varchar to int. \n \n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 2, 1))),'0','0','1','1') -- -a \n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 3, 1))),'0','0','1','1') -- -a \n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 4, 1))),'0','0','1','1') -- -a \n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 5, 1))),'0','0','1','1') -- -a \n \n... etc. \n \nThis will send the ASCII codes of every char of the hashed password through the integer covert channel. \n \n \n10) After sending enough requests, you should have the hashed admin password. Repeat the entire process to acquire the salt. \n`\n", "cvss": {"score": 6.5, "vector": "AV:N/AC:L/Au:S/C:P/I:P/A:P"}, "sourceHref": "https://packetstormsecurity.com/files/download/161918/mybb1825-sql.txt"}], "zdt": [{"lastseen": "2021-10-01T00:49:07", "description": "", "cvss3": {"exploitabilityScore": 2.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "baseScore": 8.8, "privilegesRequired": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "userInteraction": "NONE", "version": "3.1"}, "impactScore": 5.9}, "published": "2021-03-23T00:00:00", "type": "zdt", "title": "MyBB 1.8.25 - Poll Vote Count SQL Injection Vulnerability", "bulletinFamily": "exploit", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 8.0, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "PARTIAL", "availabilityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "baseScore": 6.5, "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P", "version": "2.0", "accessVector": "NETWORK", "authentication": "SINGLE"}, "acInsufInfo": false, "impactScore": 6.4, "obtainUserPrivilege": false}, "cvelist": ["CVE-2021-27889", "CVE-2021-27946"], "modified": "2021-03-23T00:00:00", "id": "1337DAY-ID-36010", "href": "https://0day.today/exploit/description/36010", "sourceData": "# Exploit Title: MyBB 1.8.25 - Poll Vote Count SQL Injection\r\n# Exploit Author: SivertPL ([email\u00a0protected])\r\n# Description: Lack of sanitization in the \"votes[]\" parameter in \"Edit Poll\" causes a second-order semi-blind SQL Injection that is triggered when performing a \"Move/Copy\" operation on the thread.\r\n# Sofware Link: https://resources.mybb.com/downloads/mybb_1825.zip\r\n# CVE: CVE-2021-27946\r\n\r\nReferences:\r\n\r\n 1) https://portswigger.net/daily-swig/chained-vulnerabilities-used-to-take-control-of-mybb-forums \r\n 2) https://vuldb.com/?id.171307\r\n 3) https://github.com/mybb/mybb/commit/aa415f08bce01f95a8319b707bb18eb67833f4c1.patch \r\n\r\nIn order to trigger the vulnerability, you must have permission to edit polls. \r\nModerators and administrators can usually do it, but in some configurations regular users can do it as well.\r\n\r\nIn case you are a moderator, the vulnerability can be used as privilege escalation provided you crack the resulting salted hash.\r\n\r\nOtherwise, you are free to use CVE-2021-27889 to impersonate the target moderator to trigger this SQL Injection from an external .js script which will perform the necessary\r\ninjections automatically, and send the resulting hashes to your server.\r\n\r\nThis is a pretty nasty vulnerability to exploit by hand (at least on regular, most common MySQL setup), but can be dangerous in the hands of \r\na very determined attacker who combines it with CVE-2021-27889 and an automated Javascript-Based SQL Injector.\r\n\r\nThis vulnerability might however allow for devastating execution of stacked queries when databases such as PostgreSQL or MS-SQL are used.\r\nIn such cases, the entire system is compromised as a result (an attacker can UPDATE the admin password and replace it with his own hash).\r\n\r\nGuide:\r\n\r\n1) Make a thread with a public poll, with multiple choices.\r\n\r\n2) Vote on at least one choice.\r\n\r\n3) Go to the \"Edit poll\" section of the poll.\r\n\r\n4) Place the following payload in the \"vote count\" input (any entry within the votes[] parameter in the resulting POST request).\r\n\r\n 1','2',ascii((select version())),'0','0','1','1') -- -a\r\n\r\n5) Save the poll.\r\n\r\n6) Perform a \"Move/Copy\" operation on the thread, moving it to a different forum, or making a copy in the same forum.\r\n\r\nThis is where the SQL Injection is triggered, and you should see an SQL Error here if the payload is incorrect.\r\n\r\n7) Go to the copied/moved version of the thread (you should be redirected there automatically).\r\n\r\n8) Go to the \"Show Results\" section of the poll.\r\n\r\n9) The total vote count under the poll is our 64 bit unsigned integer covert channel to retrieve information from the ascii select query. \r\n\r\nSince this vulnerability is semi-blind, you can only retrieve the output of the SELECT query as an unsigned integer (hence we use ASCII()).\r\nOther parameters in the INSERT query that we are injecting into are either too small, or unfeasible. \r\nUnsigned integer provides enough space to extract required data when enough requests are made.\r\n\r\nIn this case, the number is the ASCII code of the first character of the result of the injected select version() query.\r\nThis way we can transfer the output through this covert channel, one character at a time.\r\n\r\nIn order to extract the admin hash, one has to either perform many requests (so it's best to automate it), or find a better way to convert a substring varchar to int.\r\n\r\n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 2, 1))),'0','0','1','1') -- -a\r\n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 3, 1))),'0','0','1','1') -- -a\r\n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 4, 1))),'0','0','1','1') -- -a\r\n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 5, 1))),'0','0','1','1') -- -a\r\n\r\n... etc.\r\n\r\nThis will send the ASCII codes of every char of the hashed password through the integer covert channel.\r\n\r\n\r\n10) After sending enough requests, you should have the hashed admin password. Repeat the entire process to acquire the salt.\n\n# 0day.today [2021-10-01] #", "sourceHref": "https://0day.today/exploit/36010", "cvss": {"score": 6.5, "vector": "AV:N/AC:L/Au:S/C:P/I:P/A:P"}}], "exploitdb": [{"lastseen": "2022-05-13T17:39:04", "description": "", "cvss3": {"exploitabilityScore": 2.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "baseScore": 8.8, "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "version": "3.1", "userInteraction": "NONE"}, "impactScore": 5.9}, "published": "2021-03-23T00:00:00", "type": "exploitdb", "title": "MyBB 1.8.25 - Poll Vote Count SQL Injection", "bulletinFamily": "exploit", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 8.0, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "PARTIAL", "availabilityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "baseScore": 6.5, "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P", "version": "2.0", "accessVector": "NETWORK", "authentication": "SINGLE"}, "impactScore": 6.4, "acInsufInfo": false, "obtainUserPrivilege": false}, "cvelist": ["2021-27946", "CVE-2021-27889", "CVE-2021-27946"], "modified": "2021-03-23T00:00:00", "id": "EDB-ID:49699", "href": "https://www.exploit-db.com/exploits/49699", "sourceData": "# Exploit Title: MyBB 1.8.25 - Poll Vote Count SQL Injection\r\n# Exploit Author: SivertPL (kroppoloe@protonmail.ch)\r\n# Date: 20.03.2021\r\n# Description: Lack of sanitization in the \"votes[]\" parameter in \"Edit Poll\" causes a second-order semi-blind SQL Injection that is triggered when performing a \"Move/Copy\" operation on the thread.\r\n# Sofware Link: https://resources.mybb.com/downloads/mybb_1825.zip\r\n# CVE: CVE-2021-27946\r\n\r\nReferences:\r\n\r\n 1) https://portswigger.net/daily-swig/chained-vulnerabilities-used-to-take-control-of-mybb-forums \r\n 2) https://vuldb.com/?id.171307\r\n 3) https://github.com/mybb/mybb/commit/aa415f08bce01f95a8319b707bb18eb67833f4c1.patch \r\n\r\nIn order to trigger the vulnerability, you must have permission to edit polls. \r\nModerators and administrators can usually do it, but in some configurations regular users can do it as well.\r\n\r\nIn case you are a moderator, the vulnerability can be used as privilege escalation provided you crack the resulting salted hash.\r\n\r\nOtherwise, you are free to use CVE-2021-27889 to impersonate the target moderator to trigger this SQL Injection from an external .js script which will perform the necessary\r\ninjections automatically, and send the resulting hashes to your server.\r\n\r\nThis is a pretty nasty vulnerability to exploit by hand (at least on regular, most common MySQL setup), but can be dangerous in the hands of \r\na very determined attacker who combines it with CVE-2021-27889 and an automated Javascript-Based SQL Injector.\r\n\r\nThis vulnerability might however allow for devastating execution of stacked queries when databases such as PostgreSQL or MS-SQL are used.\r\nIn such cases, the entire system is compromised as a result (an attacker can UPDATE the admin password and replace it with his own hash).\r\n\r\nGuide:\r\n\r\n1) Make a thread with a public poll, with multiple choices.\r\n\r\n2) Vote on at least one choice.\r\n\r\n3) Go to the \"Edit poll\" section of the poll.\r\n\r\n4) Place the following payload in the \"vote count\" input (any entry within the votes[] parameter in the resulting POST request).\r\n\r\n 1','2',ascii((select version())),'0','0','1','1') -- -a\r\n\r\n5) Save the poll.\r\n\r\n6) Perform a \"Move/Copy\" operation on the thread, moving it to a different forum, or making a copy in the same forum.\r\n\r\nThis is where the SQL Injection is triggered, and you should see an SQL Error here if the payload is incorrect.\r\n\r\n7) Go to the copied/moved version of the thread (you should be redirected there automatically).\r\n\r\n8) Go to the \"Show Results\" section of the poll.\r\n\r\n9) The total vote count under the poll is our 64 bit unsigned integer covert channel to retrieve information from the ascii select query. \r\n\r\nSince this vulnerability is semi-blind, you can only retrieve the output of the SELECT query as an unsigned integer (hence we use ASCII()).\r\nOther parameters in the INSERT query that we are injecting into are either too small, or unfeasible. \r\nUnsigned integer provides enough space to extract required data when enough requests are made.\r\n\r\nIn this case, the number is the ASCII code of the first character of the result of the injected select version() query.\r\nThis way we can transfer the output through this covert channel, one character at a time.\r\n\r\nIn order to extract the admin hash, one has to either perform many requests (so it's best to automate it), or find a better way to convert a substring varchar to int.\r\n\r\n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 2, 1))),'0','0','1','1') -- -a\r\n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 3, 1))),'0','0','1','1') -- -a\r\n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 4, 1))),'0','0','1','1') -- -a\r\n1','2',ascii((substring((SELECT password FROM mybb_users WHERE username=\"sivertpl\"), 5, 1))),'0','0','1','1') -- -a\r\n\r\n... etc.\r\n\r\nThis will send the ASCII codes of every char of the hashed password through the integer covert channel.\r\n\r\n\r\n10) After sending enough requests, you should have the hashed admin password. Repeat the entire process to acquire the salt.", "sourceHref": "https://www.exploit-db.com/download/49699", "cvss": {"score": 6.5, "vector": "AV:N/AC:L/Au:S/C:P/I:P/A:P"}}], "thn": [{"lastseen": "2022-05-09T12:38:26", "description": "[](<https://thehackernews.com/images/-VYbGanTVJLw/YFNO_wuzwVI/AAAAAAAACDw/sbjkgjkY8R856b9AlWi9YQsis2JTdRM9gCLcBGAsYHQ/s0/mybb.jpg>)\n\nA pair of critical vulnerabilities in a popular bulletin board software called MyBB could have been chained together to achieve remote code execution (RCE) without the need for prior access to a privileged account.\n\nThe flaws, which were discovered by independent security researchers Simon Scannell and Carl Smith, were reported to the MyBB Team on February 22, following which it [released](<https://blog.mybb.com/2021/03/10/mybb-1-8-26-released-security-release/>) an update (version 1.8.26) on March 10 addressing the issues.\n\nMyBB, formerly MyBBoard and originally MyBulletinBoard, is free and open-source forum software developed using PHP and MySQL. According to internet assets search engine Spyse, there are at least [2,100 potentially vulnerable domains](<https://spyse.com/target/technology/MyBB>) that have MyBB installed.\n\nAccording to the researchers, the first issue \u2014 a nested auto URL persistent XSS vulnerability (CVE-2021-27889) \u2014 stems from how MyBB parses messages containing URLs during the rendering process, thus enabling any unprivileged forum user to embed stored XSS payloads into threads, posts, and even private messages.\n\n\"The vulnerability can be exploited with minimal user interaction by saving a maliciously crafted MyCode message on the server (e.g. as a post or Private Message) and pointing a victim to a page where the content is parsed,\" MyBB [said](<https://github.com/mybb/mybb/security/advisories/GHSA-xhj7-3349-mqcm>) in an advisory.\n\nThe second vulnerability concerns an SQL injection ([CVE-2021-27890](<https://github.com/mybb/mybb/security/advisories/GHSA-r34m-ccm8-mfhq>)) in a forum's theme manager that could result in an authenticated RCE. A successful exploitation occurs when a forum administrator with the \"Can manage themes?\" permission imports a maliciously crafted theme, or a user, for whom the theme has been set, visits a forum page. \n\n\"A sophisticated attacker could develop an exploit for the Stored XSS vulnerability and then send a private message to a targeted administrator of a MyBB board,\" the researchers [outlined](<https://blog.sonarsource.com/mybb-remote-code-execution-chain>) in a technical write-up. \"As soon as the administrator opens the private message, on his own trusted forum, the exploit triggers. An RCE vulnerability is automatically exploited in the background and leads to a full takeover of the targeted MyBB forum.\"\n\nBesides the two aforementioned vulnerabilities, version 1.8.26 also resolves four other security shortcomings that were identified by the MyBB Team, including \u2014\n\n * [CVE-2021-27946](<https://github.com/mybb/mybb/security/advisories/GHSA-23m9-w75q-ph4p>) \\- Improper validation of the number of votes in thread poll options, leading to SQL injection\n * [CVE-2021-27947](<https://github.com/mybb/mybb/security/advisories/GHSA-jjx8-8mcp-7h65>) \\- Improper sanitization of certain forum data, causing SQL injection when used in subsequent queries\n * [CVE-2021-27948](<https://github.com/mybb/mybb/security/advisories/GHSA-3p9w-2q65-r6g2>) \\- Additional User Groups ID numbers can be saved without proper validation in the Admin Control Panel, resulting in SQL injection, and\n * [CVE-2021-27949](<https://github.com/mybb/mybb/security/advisories/GHSA-cmmr-39v8-8rx2>) \\- A reflected XSS vulnerability in custom Moderator Tools, when user input attached to CSRF token-protected POST requests is not properly sanitized\n\nMyBB users are advised to upgrade to the [latest version](<https://mybb.com/versions/1.8.26/>) to mitigate the risk associated with the flaws.\n\n \n\n\nFound this article interesting? Follow THN on [Facebook](<https://www.facebook.com/thehackernews>), [Twitter _\uf099_](<https://twitter.com/thehackersnews>) and [LinkedIn](<https://www.linkedin.com/company/thehackernews/>) to read more exclusive content we post.\n", "cvss3": {"exploitabilityScore": 2.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "baseScore": 8.8, "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "version": "3.1", "userInteraction": "REQUIRED"}, "impactScore": 5.9}, "published": "2021-03-18T16:08:00", "type": "thn", "title": "Critical RCE Flaw Reported in MyBB Forum Software\u2014Patch Your Sites", "bulletinFamily": "info", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 8.6, "obtainAllPrivilege": false, "userInteractionRequired": true, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "PARTIAL", "availabilityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "baseScore": 6.8, "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 6.4, "acInsufInfo": false, "obtainUserPrivilege": false}, "cvelist": ["CVE-2021-27889", "CVE-2021-27890", "CVE-2021-27946", "CVE-2021-27947", "CVE-2021-27948", "CVE-2021-27949"], "modified": "2021-03-22T06:29:16", "id": "THN:3152B45B015211515D21C5C8A05763F5", "href": "https://thehackernews.com/2021/03/critical-rce-flaw-reported-in-mybb.html", "cvss": {"score": 6.8, "vector": "AV:N/AC:M/Au:N/C:P/I:P/A:P"}}]}