FKIE_CVE-2025-11195

Vulnerability from fkie_nvd - Published: 2025-09-30 18:15 - Updated: 2025-10-08 14:15
Severity ?
3.3 (Low) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Summary
Rapid7 AppSpider Pro versions below 7.5.021 suffer from a project name validation vulnerability, whereby an attacker can change the project name directly in the configuration file to a name that already exists. This issue stems from a lack of effective verification of the uniqueness of project names when editing them outside the application in affected versions. This vulnerability was remediated in version 7.5.021 of the product.
References
cve@rapid7.comhttps://docs.rapid7.com/insight/releasenotes-2025sep/#application-security-insightappsec-and-appspiderVendor Advisory
Impacted products
Vendor Product Version
rapid7 appspider_pro *
To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:rapid7:appspider_pro:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "6B4810BF-FEF3-4E95-B968-B85651369A88",
              "versionEndExcluding": "7.5.021",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Rapid7 AppSpider Pro versions below 7.5.021 suffer from a project name validation vulnerability, whereby an attacker can change the project name directly in the configuration file to a name that already exists. This issue stems from a lack of effective verification of the uniqueness of project names when editing them outside the application in affected versions. This vulnerability was remediated in version 7.5.021 of the product."
    },
    {
      "lang": "es",
      "value": "Las versiones de Rapid7 AppSpider Pro anteriores a la 7.5.021 sufren de una vulnerabilidad de validaci\u00f3n de nombres de proyecto, mediante la cual un atacante puede cambiar el nombre del proyecto directamente en el archivo de configuraci\u00f3n a un nombre que ya existe. Este problema se deriva de una falta de verificaci\u00f3n efectiva de la unicidad de los nombres de proyecto al editarlos fuera de la aplicaci\u00f3n en las versiones afectadas. Esta vulnerabilidad fue remediada en la versi\u00f3n 7.5.021 del producto."
    }
  ],
  "id": "CVE-2025-11195",
  "lastModified": "2025-10-08T14:15:51.740",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "NONE",
          "baseScore": 3.3,
          "baseSeverity": "LOW",
          "confidentialityImpact": "NONE",
          "integrityImpact": "LOW",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.8,
        "impactScore": 1.4,
        "source": "cve@rapid7.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-09-30T18:15:49.090",
  "references": [
    {
      "source": "cve@rapid7.com",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://docs.rapid7.com/insight/releasenotes-2025sep/#application-security-insightappsec-and-appspider"
    }
  ],
  "sourceIdentifier": "cve@rapid7.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-20"
        },
        {
          "lang": "en",
          "value": "CWE-345"
        }
      ],
      "source": "cve@rapid7.com",
      "type": "Secondary"
    },
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-345"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.