J-BusinessDirectory (com_jbusinessdirectory) 4.9.8 to 6.2.2 - Unauthenticated Arbitrary File Upload and Path Traversal (RCE, CVSS 10.0), Unauthenticated SQL Injection and Seven Further Issues

CMSJunkie released J-BusinessDirectory 6.2.3 on 31 July 2026 to fix eight security issues found during their own security review. The technical detail was withheld at the time and was published as CVEs on 19 August 2026, all of them stated as affecting 1.0.0 to 6.2.2. The most serious, CVE-2026-75949 (CVSS 10.0), is an unauthenticated arbitrary file upload and deletion: the upload and remove handlers accepted a client-controlled path root (_path_type could be pointed at the component site or admin trees), enforced no path containment, used a weak file extension check, and carried no CSRF token, which gives an anonymous attacker remote code execution and arbitrary file deletion. CVE-2026-75954 (CVSS 9.3) is an unauthenticated SQL injection in the trips search, where the search keywords and the ORDER BY clause were concatenated into the query. CVE-2026-75956 (CVSS 8.7) is a denial of service through untyped pagination parameters, where an array such as limitstart[] triggers PHP type errors and limit was never validated. CVE-2026-75950 and CVE-2026-75951 (both CVSS 6.9) are an unauthenticated listing ownership takeover using attacker-supplied company and user IDs, including for listings that already had an owner, and insecure direct object references across multiple front-end and API actions. CVE-2026-75955 (CVSS 5.1) is a reflected XSS and XML injection via an unescaped companyName written into an XML attribute. CVE-2026-75952 (CVSS 4.6) is missing CSRF tokens on many state-changing tasks: contact and quote forms, cart, bookmarks, uploads, messages, AI text generation, and several administrator actions. CVE-2026-75953 is an open mail relay, taking the recipient address from the request (contact_id_offer / contact_id_event) rather than the stored offer or event record. Also inside this range is CVE-2020-5182, reverse tabnabbing on the user-supplied business website link, fixed in 5.2.9. Update to 6.2.5 or later rather than stopping at 6.2.3: CMSJunkie shipped two further security releases (6.2.4 on 7 August and 6.2.5 on 14 August 2026), so 6.2.3 and 6.2.4 are still flagged. The JBD Apps add-ons must be updated to their own latest versions as well. Until you can update, treat the site as exposed to unauthenticated remote code execution: restrict front-end access to the directory and review the site for unexpected users, listings and PHP files under the component media and upload folders.

How severe CVE-2020-5182 is

The published CVE record has no CVSS score, so there is no vector to break down here. mySites.guru rates it Critical, and that is the rating your sites are checked against.

Timeline

1. 3 February 2020CVE-2020-5182 record published by its CNA
2. 19 August 2026mySites.guru check added for J-BusinessDirectory (after 4.9.7 up to but not including 6.2.3)

Rule details

Other vulnerabilities in J-BusinessDirectory

Updating for CVE-2020-5182 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.

References

• CVE-2020-5182 on cve.org (the official CVE record)
• CVE-2020-5182 in the NIST National Vulnerability Database
• cmsjunkie.com/news/j-businessdirectory-v6-2-3-important-security-updat