Skip to content

Vendor

wpsymposiumpro vulnerabilities

8 published CVES affecting wpsymposiumpro, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
8
Critical
0
High
1
Medium
7
Low
0
Unscored
0
CISA KEV
0
Atom feed of wpsymposiumpro alerts

Products

Latest wpsymposiumpro CVEs

Newest publication first

  1. HighCVSS 7.5 EPSS 59.0% Framework module Public exploit

    Unrestricted file upload vulnerability in UploadHandler.php in the WP Symposium plugin 14.11 for WordPress allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in server/php/.

  2. MediumCVSS 4.3 EPSS 1.7%

    Multiple cross-site scripting (XSS) vulnerabilities in the WP Symposium plugin before 14.11 for WordPress allow remote attackers to inject arbitrary web script or HTML via the (1) text parameter in an addComment action to ajax/profile_functions.php, (2) compose_text parameter in...

  3. MediumCVSS 6.5 EPSS 3.6% Public exploit

    SQL injection vulnerability in ajax/mail_functions.php in the WP Symposium plugin before 14.11 for WordPress allows remote authenticated users to execute arbitrary SQL commands via the tray parameter in a getMailMessage action.

  4. MediumCVSS 4.3 EPSS 1.6%

    Cross-site scripting (XSS) vulnerability in invite.php in the WP Symposium plugin before 13.04 for WordPress allows remote attackers to inject arbitrary web script or HTML via the u parameter.

  5. MediumCVSS 5.8 EPSS 2.0%

    Open redirect vulnerability in invite.php in the WP Symposium plugin 13.04 for WordPress allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the u parameter.

  6. MediumCVSS 4.3 EPSS 2.3%

    Cross-site scripting (XSS) vulnerability in uploadify/get_profile_avatar.php in the WP Symposium plugin before 11.12.08 for WordPress allows remote attackers to inject arbitrary web script or HTML via the uid parameter.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.