What is the CVSS score of CVE-2019-16520?

CVE-2019-16520 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 1.5%.

Is there a public PoC exploit available for CVE-2019-16520?

Yes, a public proof-of-concept exploit is available for CVE-2019-16520. Prioritise patching immediately. EPSS: 1.5%.

Is there a patch available for CVE-2019-16520?

Yes, a patch is available for CVE-2019-16520. Update the affected software to the latest version immediately.

All In One Seo Pack CVE-2019-16520

MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2019-10-16 cve@mitre.org

XSS WordPress All In One Seo Pack

5.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Oct 16, 2019 - 14:15 nvd

MEDIUM 5.4

DescriptionNVD

The all-in-one-seo-pack plugin before 3.2.7 for WordPress (aka All in One SEO Pack) is susceptible to Stored XSS due to improper encoding of the SEO-specific description for posts provided by the plugin via unsafe placeholder replacement.

AnalysisAI

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. The all-in-one-seo-pack plugin before 3.2.7 for WordPress (aka All in One SEO Pack) is susceptible to Stored XSS due to improper encoding of the SEO-specific description for posts provided by the plugin via unsafe placeholder replacement. Affected products include: Semperplugins All In One Seo Pack. Version information: before 3.2.7.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.