Joomla Security News

Keep up to date with the latest Joomla Security News.

    • Project: Joomla!
    • SubProject: CMS
    • Impact:Moderate
    • Severity: Low
    • Versions: 2.5.0 through 3.8.12
    • Exploit type: CSRF
    • Reported Date: 2018-September-26
    • Fixed Date: 2018-October-02
    • CVE Number: CVE-2018-17858

    Description

    Added additional CSRF hardening in com_installer actions in the backend.

    Affected Installs

    Joomla! CMS versions 2.5.0 through 3.8.12

    Solution

    Upgrade to version 3.8.13

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By:Raviraj A. Powar
    • Project: Joomla!
    • SubProject: CMS
    • Impact:Moderate
    • Severity: Low
    • Versions: 1.5.0 through 3.8.12
    • Exploit type: ACL Violation
    • Reported Date: 2017-December-27
    • Fixed Date: 2018-October-02
    • CVE Number: CVE-2018-17855

    Description

    In case that an attacker gets access to the mail account of an user who can approve admin verifications in the registration process he can activate himself.

    Affected Installs

    Joomla! CMS versions 1.5.0 through 3.8.12

    Solution

    Upgrade to version 3.8.13

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By:Paul Freeman
    • Project: Joomla!
    • SubProject: CMS
    • Impact:Moderate
    • Severity: Low
    • Versions: 3.1.0 through 3.8.12
    • Exploit type: ACL Violation
    • Reported Date: 2018-June-20
    • Fixed Date: 2018-October-02
    • CVE Number: CVE-2018-17857

    Description

    Inadequate checks on the tags search fields can lead to an access level violation.

    Affected Installs

    Joomla! CMS versions 3.1.0 through 3.8.12

    Solution

    Upgrade to version 3.8.13

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By:Андрей Капитанов
    • Project: Joomla!
    • SubProject: CMS
    • Impact:High
    • Severity: Low
    • Versions: 2.5.4 through 3.8.12
    • Exploit type: Object Injection
    • Reported Date: 2018-June-21
    • Fixed Date: 2018-October-02
    • CVE Number: CVE-2018-17856

    Description

    Joomla’s com_joomlaupdate allows the execution of arbitrary code. The default ACL config enabled access of Administrator-level users to access com_joomlaupdate and trigger a code execution.

    Affected Installs

    Joomla! CMS versions 2.5.4 through 3.8.12

    Solution

    Upgrade to version 3.8.13

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By:Codesafescan
    • Project: Joomla!
    • SubProject: CMS
    • Impact:Moderate
    • Severity: Low
    • Versions: 2.5.0 through 3.8.12
    • Exploit type: Incorrect Access Control
    • Reported Date: 2018-September-17
    • Fixed Date: 2018-October-02
    • CVE Number: CVE-2018-17859

    Description

    Inadequate checks in com_contact could allowed mail submission in disabled forms.

    Affected Installs

    Joomla! CMS versions 2.5.0 through 3.8.12

    Solution

    Upgrade to version 3.8.13

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By: David Jardin (JSST)
    • Project: Joomla!
    • SubProject: CMS
    • Impact:Low
    • Severity: Low
    • Versions: 3.7.0 through 3.8.11
    • Exploit type: ACL Violation
    • Reported Date: 2018-July-10
    • Fixed Date: 2018-August-28
    • CVE Number: CVE-2018-15881

    Description

    Inadequate checks regarding disabled fields can lead to an ACL violation.

    Affected Installs

    Joomla! CMS versions 3.7.0 through 3.8.11

    Solution

    Upgrade to version 3.8.12

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By:Elisa Foltyn, COOLCAT CREATIONS
    • Project: Joomla!
    • SubProject: CMS
    • Impact:Low
    • Severity: Low
    • Versions: 1.5.0 through 3.8.11
    • Exploit type: XSS
    • Reported Date: 2018-July-10
    • Fixed Date: 2018-August-28
    • CVE Number: CVE-2018-15880

    Description

    Inadequate output filtering on the user profile page could lead to a stored XSS attack.

    Affected Installs

    Joomla! CMS versions 1.5.0 through 3.8.11

    Solution

    Upgrade to version 3.8.12

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By: Fouad Maakor
    • Project: Joomla!
    • SubProject: CMS
    • Impact:High
    • Severity: Low
    • Versions: 1.5.0 through 3.8.11
    • Exploit type: Malicious file upload
    • Reported Date: 2018-August-23
    • Fixed Date: 2018-August-28
    • CVE Number: CVE-2018-15882

    Description

    Inadequate checks in the InputFilter class could allow specifically prepared PHAR files to pass the upload filter.

    Affected Installs

    Joomla! CMS versions 1.5.0 through 3.8.11

    Solution

    Upgrade to version 3.8.12

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By:Davide Tampellini
    • Project: Joomla!
    • SubProject: CMS
    • Impact:Low
    • Severity: Low
    • Versions: 1.6.0 through 3.8.8
    • Exploit type: XSS
    • Reported Date: 2018-May-07
    • Fixed Date: 2018-June-26
    • CVE Number: CVE-2018-12711

    Description

    In some cases the link of the current language might contain unescaped HTML special characters. This may lead to reflective XSS via injection of arbitrary parameters and/or values on the current page url.

    Affected Installs

    Joomla! CMS versions 1.6.0 through 3.8.8

    Solution

    Upgrade to version 3.8.9

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By:Borja Lorenzo, Innotecsystem
    • Project: Joomla!
    • SubProject: CMS
    • Impact:Low
    • Severity: Low
    • Versions: 2.5.0 through 3.8.8
    • Exploit type: LFI
    • Reported Date: 2018-April-23
    • Fixed Date: 2018-June-26
    • CVE Number: CVE-2018-12712

    Description

    Our autoload code checks classnames to be valid, using the "class_exists" function in PHP. In PHP 5.3 this function validates invalid names as valid, which can result in a Local File Inclusion.

    Affected Installs

    Joomla! CMS versions 2.5.0 through 3.8.8

    Solution

    Upgrade to version 3.8.9

    Contact

    The JSST at the Joomla! Security Centre.

    Reported By:Davide Tampellini