Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-13687: CWE-862 Missing Authorization in labibahmed42 Team Builder – Meet the Team

0
Medium
VulnerabilityCVE-2024-13687cvecve-2024-13687cwe-862
Published: Tue Feb 18 2025 (02/18/2025, 04:21:18 UTC)
Source: CVE Database V5
Vendor/Project: labibahmed42
Product: Team Builder – Meet the Team

Description

CVE-2024-13687 is a medium severity vulnerability in the WordPress plugin 'Team Builder – Meet the Team' by labibahmed42. The flaw arises from a missing authorization check in the save_team_builder_options() function, allowing authenticated users with Subscriber-level access or higher to modify plugin settings without proper permissions. This vulnerability affects all versions up to and including 1. 3. Exploitation does not require user interaction and can be performed remotely over the network. Although it does not impact confidentiality or availability, it allows unauthorized integrity modification of plugin configuration, potentially leading to further misuse or privilege escalation. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize applying patches or implementing access restrictions to mitigate risk.

AI-Powered Analysis

AILast updated: 02/25/2026, 22:47:32 UTC

Technical Analysis

The vulnerability identified as CVE-2024-13687 affects the 'Team Builder – Meet the Team' WordPress plugin developed by labibahmed42. The root cause is a missing capability check in the save_team_builder_options() function, which is responsible for saving the plugin's configuration settings. Due to this missing authorization control, any authenticated user with at least Subscriber-level privileges can invoke this function to modify plugin settings. Since WordPress Subscriber roles are typically assigned to low-privileged users, this vulnerability effectively allows unauthorized users to alter plugin behavior without administrative approval. The vulnerability is present in all versions up to and including 1.3. The CVSS v3.1 base score is 4.3 (medium severity), reflecting that the attack vector is network-based, requires low privileges, and no user interaction, but only impacts integrity without affecting confidentiality or availability. The scope remains unchanged as the vulnerability affects only the plugin itself. No patches are currently linked, and no known exploits have been reported in the wild, but the risk remains due to the ease of exploitation by authenticated users. This vulnerability falls under CWE-862 (Missing Authorization), highlighting the failure to properly verify user permissions before allowing sensitive operations.

Potential Impact

The primary impact of CVE-2024-13687 is unauthorized modification of plugin settings by low-privileged authenticated users. This can lead to altered plugin behavior, which may be leveraged to introduce malicious content, disrupt site functionality, or facilitate further attacks such as privilege escalation or persistent backdoors if the plugin controls critical site components. While it does not directly expose sensitive data or cause denial of service, the integrity compromise can undermine trust in the affected WordPress site and potentially impact site administrators and end users. Organizations relying on this plugin, especially those with multiple user roles including Subscribers, face increased risk of internal misuse or exploitation by compromised accounts. The vulnerability's network accessibility and lack of user interaction requirement make it easier to exploit in multi-user environments. Overall, the impact is moderate but significant enough to warrant prompt mitigation to prevent misuse and maintain site integrity.

Mitigation Recommendations

To mitigate CVE-2024-13687, organizations should first check for updates or patches from the plugin developer and apply them immediately once available. In the absence of an official patch, administrators should restrict Subscriber-level users from accessing or interacting with the plugin's settings interface, either by adjusting user roles and capabilities or using additional access control plugins to enforce stricter permissions. Reviewing and hardening WordPress user roles to minimize unnecessary privileges can reduce the attack surface. Monitoring plugin configuration changes and implementing logging can help detect unauthorized modifications early. Additionally, consider disabling or removing the plugin if it is not essential to reduce risk exposure. Regular security audits and vulnerability scanning focusing on installed plugins will help identify similar issues proactively. Finally, educating site administrators about the risks of low-privileged user accounts and enforcing strong authentication practices can further reduce exploitation likelihood.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-23T18:59:04.039Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e68b7ef31ef0b5a0178

Added to database: 2/25/2026, 9:49:28 PM

Last enriched: 2/25/2026, 10:47:32 PM

Last updated: 2/26/2026, 5:56:16 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats