← WordPress Vulnerabilities
WordPress security by component

Contact Us page - Contact people LITE

Contact Us page - Contact people LITE is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Jul 04, 2025; the highest published CVSS base score is 8.5.

Plugin slug: contact-us-page-contact-people

CVE-2025-28967: Contact Us page - Contact people LITE: SQL injection

Contact Us page - Contact people LITE is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.

PublishedJul 04, 2025
Safe version guidanceSee mitigation notes
Published vulnerabilities for contact-us-page-contact-people
Safe version
Jul 04, 2025 CVE-2025-28967
Contact Us page - Contact people LITE: SQL injection
Contact Us page - Contact people LITE is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
See mitigation notes
CVE8.5
NVDPending
Jun 13, 2025 CVE-2025-5123
Contact Us Page – Contact People: Cross-site scripting
Contact Us Page – Contact People is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
See mitigation notes
CVE6.4
NVD5.4
Mar 01, 2023 CVE-2023-23973
Contact Us Page Contact People: Cross-site request forgery
Contact Us Page Contact People is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
See mitigation notes
CVE4.3
NVD6.5