Scott Reilly vulnerabilities

Products

• Commenter Emails 1
• Configure SMTP 1
• Get Custom Field Values 1
• Post-to-Post Links 1
• Preserve Code Formatting 1

Latest Scott Reilly CVEs

Newest publication first

1. CVE-2025-49386 WordPress Preserve Code Formatting Plugin <= 4.0.1 - PHP Object Injection Vulnerability

   Published 2025-11-06

   High·CVSS 8.8 EPSS 0.46%

   Deserialization of Untrusted Data vulnerability in Scott Reilly Preserve Code Formatting preserve-code-formatting allows Object Injection.This issue affects Preserve Code Formatting: from n/a through <= 4.0.1.

2. CVE-2025-23878 WordPress Post-to-Post Links plugin <= 4.2 - Cross Site Scripting (XSS) vulnerability

   Published 2025-01-16

   Medium·CVSS 5.9 EPSS 0.39%

   Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Scott Reilly Post-to-Post Links easy-post-to-post-links allows Stored XSS.This issue affects Post-to-Post Links: from n/a through <= 4.2.

3. CVE-2024-27192 WordPress Configure SMTP Plugin <= 3.1 is vulnerable to Cross Site Scripting (XSS)

   Published 2024-03-15

   High·CVSS 7.1 EPSS 0.35%

   Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Scott Reilly Configure SMTP allows Reflected XSS.This issue affects Configure SMTP: from n/a through 3.1.

4. CVE-2022-45360 WordPress Commenter Emails Plugin <= 2.6.1 is vulnerable to CSV Injection

   Published 2023-11-07

   Critical·CVSS 9.8 EPSS 0.64%

   Improper Neutralization of Formula Elements in a CSV File vulnerability in Scott Reilly Commenter Emails.This issue affects Commenter Emails: from n/a through 2.6.1.

5. CVE-2023-45604 WordPress Get Custom Field Values Plugin <= 4.0.1 is vulnerable to Cross Site Scripting (XSS)

   Published 2023-10-18

   Medium·CVSS 4.8 EPSS 0.37%

   Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Scott Reilly Get Custom Field Values plugin <= 4.0.1 versions.

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.