CVE-2025-47646 is a weak password recovery vulnerability in Gilblas Ngunte Possi PSW Front-end Login & Registration affecting versions through 1.13. The issue is described as a weak forgotten-password or password recovery mechanism that allows password recovery exploitation. Based on the available information, the flaw resides in the application's password reset or account recovery workflow, where the recovery process does not provide sufficient assurance that the requester is the legitimate account owner.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a Python proof-of-concept exploit for CVE-2025-47646, targeting the WordPress PSW Front-end Login Registration Plugin version 1.12 or below. The exploit leverages an unauthenticated privilege escalation vulnerability by sending a crafted POST request to the /wp-admin/admin-ajax.php endpoint, using the 'register_user_front_end' action and a specific 'psw_form' value. The script allows an attacker to register a new user account on the target WordPress site without authentication, which could be used for further privilege escalation depending on site configuration. The repository consists of two files: the main exploit script (CVE-2025-47646.py) and a README.md with usage instructions and details about the vulnerability. The exploit requires Python 3 and the 'requests' and 'pyfiglet' libraries. No hardcoded credentials or fake/dangerous commands are present; the script is a functional PoC for the described vulnerability.
6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.