S4E just found a high online generic sql injection vulnerability scanner
medium·Product Based Web Vulnerabilities·Updated Jul 28, 2026

CVE-2025-14047 Scanner

CVE-2025-14047 Scanner - Missing Authorization vulnerability in WP User Frontend

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
0
Times Used
by S4E users
0
Assets Scanned
domains & IPs
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2025-14047
5.3
CVSSmedium
Exploitable remotely over the internet · no authentication required.

The Registration, User Profile, Membership, Content Restriction, User Directory, and Frontend Post Submission – WP User Frontend plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'Frontend_Form_Ajax::submit_post' function in all versions up to, and including, 4.2.4. This makes it possible for unauthenticated attackers to delete attachment.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registrationby wedevs
0
Updated Aug 19, 2026View on NVD →
Detail

The WP User Frontend is a popular plugin for WordPress, commonly utilized by site owners to provide frontend post submission capabilities to users without accessing the WordPress backend. It allows users to submit, edit, and manage their posts, attachments, and other content directly from the frontend, enhancing user experience and site interaction. Various websites, including blogs, forums, and online communities, use this plugin to facilitate content management without opening up admin functions to all users. The plugin is developed by wedevs and is frequently updated to introduce new features and address existing issues. By focusing on frontend submissions, it appeals to site owners seeking to maintain better security by limiting backend access. The plugin's wide use and community-driven development have made it a staple in many WordPress installations.

This vulnerability revolves around missing authorization checks within certain AJAX functions of the WP User Frontend. Specifically, it allows unauthenticated users to exploit the plugin's AJAX handling, leading to potential unauthorized actions. The absence of proper capability checks in the Frontend_Form_Ajax::submit_post function is the crux of the vulnerability. Exploits can occur when public frontend forms are available, allowing attackers to issue unauthorized attachment deletion requests. This vulnerability is significant because it can lead to data loss without the need for valid user credentials. It emphasizes the need for robust authorization mechanisms within plugins handling frontend submissions to prevent unauthorized data manipulation.

The vulnerability is technically attributed to a missing capability check in the submit_post function of the Frontend_Form_Ajax class. This oversight allows unauthenticated users to issue POST requests to the plugin's AJAX endpoint, resulting in unauthorized operations such as attachment deletions. The vulnerable parameter includes the action attribute within POST requests. By manipulating this parameter, malicious actors can delete attachments associated with frontend forms without legitimate access. The exposure is critical in public-facing forms where any visitor can initiate such deletions, underlining the importance of comprehensive checks before executing sensitive operations. Exploit scenarios emphasize the risks for sites relying on this plugin for user-generated content.

If exploited by malicious actors, this vulnerability can lead to significant data loss, particularly concerning media attachments submitted through the site's frontend. Unauthorized deletion of attachments may impact the integrity and availability of user-uploaded content, which is essential for sites relying on media-rich submissions. The potential for data loss poses risks for data integrity, user satisfaction, and site credibility. In severe cases, it may lead to a partial or full compromise of media content integrity across the platform, potentially necessitating rollback measures or loss of crucial user-generated data. This vulnerability highlights the need to provision for data confidentiality and integrity when deploying plugins.

REFERENCES

Solution Advice
  • Update WP User Frontend to version 4.2.5 or later.
  • Implement a comprehensive capability check for AJAX functions handling data operations.
  • Restrict public access to critical AJAX endpoints through proper authentication measures.
  • Consider implementing a logging mechanism to monitor unauthorized AJAX requests.
  • Regularly review and audit plugin code for potential security flaws.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.

CVE-2025-14047 Scanner - Missing Authorization vulnerability in WP User Frontend S4E