CVE-2026-6400
Cross-Site Request Forgery in Child Height Predictor WordPress Plugin
Publication date: 2026-05-20
Last updated on: 2026-05-20
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ostheimer | child_height_predictor | to 1.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Child Height Predictor by Ostheimer plugin for WordPress has a Cross-Site Request Forgery (CSRF) vulnerability in all versions up to and including 1.3. This happens because the plugin's options() function, which updates plugin settings, lacks proper nonce verification. Specifically, the form template does not include a wp_nonce_field() call, and the handler does not call check_admin_referer() or wp_verify_nonce(). As a result, an attacker can trick a site administrator into clicking a malicious link or visiting a harmful page that submits a forged POST request, leading to unauthorized changes in the plugin settings.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update the Child Height Predictor by Ostheimer plugin to a version later than 1.3 where nonce verification is properly implemented.
If an update is not immediately available, avoid clicking on suspicious links or visiting untrusted pages while logged in as a site administrator, as the vulnerability allows unauthenticated attackers to trick administrators into submitting forged POST requests.
Additionally, consider applying custom patches to add nonce verification in the options() function and ensure the form template includes a wp_nonce_field() call, along with calls to check_admin_referer() or wp_verify_nonce() in the handler.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to cause unauthorized changes to the plugin settings by tricking an administrator into submitting a forged request. For example, attackers can change unit preferences or other plugin options stored in the database without the administrator's consent. While it does not directly compromise data confidentiality or availability, it can lead to integrity issues by altering plugin behavior unexpectedly.