Skip to content

← Public intelligence

Packagist package

symphonycms/symphony-2

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 1.3PackagistPublished

    Symphony CMS vulnerable to Cross-site Scripting

    CVE-2011-4340 · GHSA-wvq5-72qp-grjw

    Affected
    • Packagist symphonycms/symphony-2 < 2.2.4
    Fixed in
    2.2.4· Vendor fix available
    Issue
    Multiple cross-site scripting (XSS) vulnerabilities in Symphony CMS 2.2.3 and possibly other versions before 2.2.4 allow remote authenticated users with Author privileges to inject arbitrary web script or HTML via (1) the profile parameter to extensions/profiledevkit/content/content.profile.php, as demonstrated via requests to (a) the default URI, (b) about/, or (c) drafts/; or (2) the filter parameter in symphony/lib/core/class.symphony.php, as demonstrated via requests to (d) symphony/publish/comments or (e) symphony/publish/images. NOTE: some of these details are obtained from third party information.

    Recommended action: Upgrade to 2.2.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.1PackagistPublished

    Symphony CMS XSS Vulnerabilities

    CVE-2015-8766 · GHSA-4c5w-qqfg-grf3

    Affected
    • Packagist symphonycms/symphony-2 < 2.6.4
    Fixed in
    2.6.4· Vendor fix available
    Issue
    Multiple cross-site scripting (XSS) vulnerabilities in content/content.systempreferences.php in Symphony CMS before 2.6.4 allow remote attackers to inject arbitrary web script or HTML via the (1) emailsendmail[fromname], (2) emailsendmail[fromaddress], (3) emailsmtp[fromname], (4) emailsmtp[fromaddress], (5) emailsmtp[host], (6) emailsmtp[port], (7) jitimagemanipulation[trustedexternalsites], or (8) maintenancemode[ipwhitelist] parameters to system/preferences.

    Recommended action: Upgrade to 2.6.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →