frankkoenen login_register Plugin up to 1.2.0 on WordPress Setting login_register_login_post cross-site request forgery

Summaryinfo

A vulnerability was found in frankkoenen login_register Plugin up to 1.2.0 on WordPress. It has been rated as problematic. Affected is an unknown function of the component Setting Handler. This manipulation of the argument login_register_login_post causes cross-site request forgery. The identification of this vulnerability is CVE-2026-1503. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in frankkoenen login_register Plugin up to 1.2.0 on WordPress and classified as problematic. Affected by this vulnerability is an unknown function of the component Setting Handler. The manipulation of the argument login_register_login_post with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. The summary by CVE is:

The login_register plugin for WordPress is vulnerable to Cross-Site Request Forgery to Stored Cross-Site Scripting in all versions up to, and including, 1.2.0. This is due to missing nonce validation on the settings page and insufficient input sanitization and output escaping on the 'login_register_login_post' parameter. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via a forged request granted they can trick an administrator into performing an action such as clicking on a link.

The weakness was shared by Muhammad Nur Ibnu Hubab. It is possible to read the advisory at wordfence.com. This vulnerability is known as CVE-2026-1503 since 01/27/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 1.2.0 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• frankkoenen

Name

• login_register Plugin

Version

• 1.0
• 1.1
• 1.2.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion