User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration <= 4.3.1 - Authenticated (Subscriber+) PHP Object Injection
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to Deserialization of Untrusted Data in versions up to, and including, 4.3.1 This is due to insufficient input validation and type checking on the wpuf_files parameter during form submission, combined with unconditional deserialization via maybe_unserialize() when displaying post content. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary PHP objects, which can be leveraged to execute arbitrary code, delete arbitrary files, or perform other malicious actions if a POP chain is present on the target system.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- wedevs User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration
through 4.3.1
References 19
plugins.trac.wordpress.org
- browser/wp-user-frontend/trunk/wpuf-functions.php#L959
- browser/wp-user-frontend/tags/4.2.10/wpuf-functions.php#L959
- browser/wp-user-frontend/trunk/wpuf-functions.php#L1103
- browser/wp-user-frontend/tags/4.2.10/wpuf-functions.php#L1103
- browser/wp-user-frontend/trunk/includes/Traits/FieldableTrait.php#L679
- browser/wp-user-frontend/tags/4.2.10/includes/Traits/FieldableTrait.php#L679
- browser/wp-user-frontend/trunk/includes/Traits/FieldableTrait.php#L704
- browser/wp-user-frontend/tags/4.2.10/includes/Traits/FieldableTrait.php#L704
- browser/wp-user-frontend/trunk/includes/Traits/FieldableTrait.php#L429
- browser/wp-user-frontend/tags/4.2.10/includes/Traits/FieldableTrait.php#L429
- browser/wp-user-frontend/trunk/includes/Traits/FieldableTrait.php#L502
- browser/wp-user-frontend/tags/4.2.10/includes/Traits/FieldableTrait.php#L502
- browser/wp-user-frontend/trunk/includes/Ajax/Frontend_Form_Ajax.php#L35
- browser/wp-user-frontend/tags/4.2.10/includes/Ajax/Frontend_Form_Ajax.php#L35
- browser/wp-user-frontend/trunk/includes/Ajax/Frontend_Form_Ajax.php#L36
- browser/wp-user-frontend/tags/4.2.10/includes/Ajax/Frontend_Form_Ajax.php#L36
- changeset/3514258/wp-user-frontend/trunk/includes/Traits/FieldableTrait.php
- changeset?old_path=%2Fwp-user-frontend/tags/4.3.1&new_path=%2Fwp-user-frontend/tags/4.3.2