Sploit.io - Search

Product: I Plant A Tree, version: >= n/a, <= 1.7.3

CVE-2024-51883

Severity: MEDIUM

Description: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Micha I Plant A Tree allows Stored XSS.This issue affects I Plant A Tree: from n/a through 1.7.3.

CVSS Score: 6.5

Priority

B

CISA Data

EPSS Data

  • EPSS: 0.000430000
  • Percentile: 0.113600000
  • Date: 2025-01-17

ExploitDB

No data available.

HackerOne Data

  • Rank: 7457
  • Reports submitted count: 0
  • Unknown: 0
  • None: 0
  • Low: 0
  • Medium: 0
  • High: 0
  • Critical: 0

GitHub PoCs

    Nuclei Templates

    No data available.

    VulnCheck Data

    Affected Products:

    • Micha I Plant A Tree - Versions: n/a

    References:

    Risk Assessment

    1. Risk Assessment
    The vulnerability identified as CVE-2024-51883 is a Stored Cross-Site Scripting (XSS) issue in the WordPress plugin "I Plant A Tree" by Micha. It affects versions up to and including 1.7.3. The CVSS score of 6.5 (MEDIUM) indicates a moderate risk level. The vulnerability arises from improper neutralization of input during web page generation, allowing an attacker to inject malicious scripts into the application. These scripts are stored and executed when other users access the affected pages.

    The likelihood of exploitation is moderate due to the requirement of low privileges (PR:L) and user interaction (UI:R). However, the attack complexity is low (AC:L), making it relatively easy for an attacker to exploit if they gain access to a low-privileged account. The impact spans confidentiality (C:L), integrity (I:L), and availability (A:L), with potential outcomes including unauthorized access to sensitive data, manipulation of web content, and disruption of user experience. The scope is changed (S:C), meaning the vulnerability can affect components beyond the vulnerable plugin.

    Business impact includes reputational damage, loss of customer trust, and potential legal or regulatory consequences if sensitive data is compromised. The EPSS score of 0.000430000 suggests a low probability of active exploitation in the wild, but the risk remains significant due to the nature of the vulnerability.

    2. Potential Attack Scenarios
    An attacker with low-privileged access to the WordPress site, such as a contributor or author account, could exploit this vulnerability by injecting malicious JavaScript code into a post, page, or comment. For example, the attacker could craft a payload that steals session cookies or redirects users to a phishing site. When an administrator or another user views the compromised content, the malicious script executes in their browser, potentially allowing the attacker to hijack their session, escalate privileges, or deface the website.

    The attack vector involves the attacker logging into the WordPress dashboard, creating or editing content with the malicious payload, and saving it. The stored payload is then served to other users, including administrators, when they access the affected content. The potential outcomes include unauthorized access to sensitive information, account compromise, and disruption of website functionality.

    3. Mitigation Recommendations
    The primary mitigation for this vulnerability is to update the "I Plant A Tree" plugin to a version beyond 1.7.3, as the vendor has likely released a patch to address the issue. If an update is not available, consider disabling or removing the plugin until a fix is provided.

    Additionally, implement input validation and output encoding to prevent XSS attacks. Regularly review and restrict user permissions to minimize the risk of exploitation by low-privileged accounts. Employ a web application firewall (WAF) to detect and block XSS payloads.

    For further guidance, refer to the following resources:
    - Patchstack advisory: https://patchstack.com/database/vulnerability/i-plant-a-tree/wordpress-i-plant-a-tree-plugin-1-7-3-stored-cross-site-scripting-xss-vulnerability?_s_id=cve
    - OWASP XSS Prevention Cheat Sheet: https://owasp.org/www-project-cheat-sheets/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html

    4. Executive Summary
    CVE-2024-51883 is a Stored Cross-Site Scripting (XSS) vulnerability in the WordPress plugin "I Plant A Tree," affecting versions up to 1.7.3. Rated as a medium-risk issue, it allows attackers with low privileges to inject malicious scripts into the application, potentially compromising user data, website integrity, and availability. While the likelihood of exploitation is moderate, the ease of attack and potential business impact make this a significant concern.

    Attackers could exploit this vulnerability to hijack user sessions, deface the website, or steal sensitive information. Immediate action is required to mitigate the risk, including updating the plugin, implementing input validation, and restricting user permissions. Failure to address this vulnerability could result in reputational damage, loss of customer trust, and regulatory penalties. Prioritizing remediation is essential to safeguard the organization's digital assets and maintain operational continuity.

    CVE-2024-54331

    Severity: HIGH

    Description: Cross-Site Request Forgery (CSRF) vulnerability in Micha I Plant A Tree allows Stored XSS.This issue affects I Plant A Tree: from n/a through 1.7.3.

    CVSS Score: 7.1

    Priority

    D

    CISA Data

    EPSS Data

    • EPSS: 0.000550000
    • Percentile: 0.171680000
    • Date: 2026-04-16

    ExploitDB

    No data available.

    HackerOne Data

    • Rank: 9108
    • Reports submitted count: 0
    • Unknown: 0
    • None: 0
    • Low: 0
    • Medium: 0
    • High: 0
    • Critical: 0

    GitHub PoCs

      Nuclei Templates

      No data available.

      VulnCheck Data

      Affected Products:

      • Micha I Plant A Tree - Versions: n/a

      References:

      Risk Assessment

      1. Risk Assessment
      The vulnerability CVE-2024-54331 is a Cross-Site Request Forgery (CSRF) vulnerability leading to Stored Cross-Site Scripting (XSS) in the Micha I Plant A Tree WordPress plugin, specifically versions up to and including 1.7.3. This means an attacker can trick a logged-in user into performing an action on their behalf (CSRF), and the malicious script will be stored on the server and executed for other users (Stored XSS). The EPSS score is relatively low at 0.000550000, suggesting a limited real-world exploitation probability. However, the impact can be significant. The business impact depends on the functionality of the i-plant-a-tree plugin and how it’s integrated within the WordPress site. If the plugin handles sensitive data or allows users to perform critical actions, the impact could be high. Likelihood of exploitation is moderate, given the commonality of CSRF and XSS vulnerabilities, and the ease of exploitation is also moderate, requiring a user to be logged in and tricked into clicking a malicious link or visiting a compromised page. Confidentiality could be compromised if the XSS allows an attacker to steal cookies or session tokens. Integrity is definitely at risk, as the attacker can modify data or perform actions as the victim. Availability can be impacted if the XSS leads to a denial-of-service scenario.

      2. Potential Attack Scenarios
      An attacker could craft a malicious link disguised as a legitimate action within the WordPress site using the i-plant-a-tree plugin. For example, if the plugin allows users to donate to plant a tree, the attacker could create a link that, when clicked by a logged-in user, triggers a CSRF request to update the user's profile with a malicious JavaScript payload. This payload, stored on the server as part of the profile update, will then execute for all users viewing the affected user’s profile. The attacker could then inject a script to steal the user’s WordPress session cookie, allowing them to impersonate the user. Alternatively, the script could redirect users to a phishing site, or deface the website. The attack vector is a crafted HTML link sent via email, social media, or a compromised website. The attack process involves the victim clicking the link while logged into WordPress, triggering the CSRF request, storing the malicious script, and finally executing it when other users view the affected portion of the site. The potential outcome is account compromise, data theft, website defacement, or redirection to a malicious website.

      3. Mitigation Recommendations
      The primary mitigation is to update the i-plant-a-tree plugin to version 1.7.4 or later. This version contains the fix for the CSRF and Stored XSS vulnerability. WordPress administrators should immediately update the plugin through the WordPress admin interface (Plugins -> Installed Plugins). Additionally, consider implementing CSRF protection across all WordPress forms and actions, even those not directly affected by this vulnerability, as a general best practice. Web Application Firewalls (WAFs) can be configured to detect and block malicious XSS payloads. Regularly scan the WordPress site for vulnerabilities using a vulnerability scanner. Patchstack provides further details and the updated plugin here: https://patchstack.com/database/Wordpress/Plugin/i-plant-a-tree/vulnerability/wordpress-i-plant-a-tree-plugin-1-7-3-csrf-to-stored-cross-site-scripting-vulnerability?_s_id=cve.

      4. Executive Summary
      The Micha I Plant A Tree WordPress plugin (versions 1.7.3 and earlier) is vulnerable to a Cross-Site Request Forgery (CSRF) attack that can lead to Stored Cross-Site Scripting (XSS). This means an attacker can trick logged-in users into performing actions on their behalf, and inject malicious code that will affect other users visiting the website. While the risk is moderate, the potential impact includes account compromise, data theft, and website defacement. The most important action is to update the i-plant-a-tree plugin to version 1.7.4 or later as soon as possible. This will address the vulnerability and protect the website and its users. Addressing this vulnerability is crucial to maintain the integrity and security of the website and ensure a positive user experience. Delaying the update could leave the website open to potential attacks and data breaches.