fkie_cve-2025-25222
Vulnerability from fkie_nvd
Published
2025-02-18 01:15
Modified
2025-02-18 01:15
Severity ?
7.3 (High) - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Summary
The LuxCal Web Calendar prior to 5.3.3M (MySQL version) and prior to 5.3.3L (SQLite version) contains an SQL injection vulnerability in retrieve.php. If this vulnerability is exploited, information in a database may be deleted, altered, or retrieved.
References
vultures@jpcert.or.jphttps://jvn.jp/en/jp/JVN26024080/
vultures@jpcert.or.jphttps://www.luxsoft.eu/?download
vultures@jpcert.or.jphttps://www.luxsoft.eu/lcforum/viewtopic.php?pid=1984#p1984
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "The LuxCal Web Calendar prior to 5.3.3M (MySQL version) and prior to 5.3.3L (SQLite version) contains an SQL injection vulnerability in retrieve.php. If this vulnerability is exploited, information in a database may be deleted, altered, or retrieved.",
      },
      {
         lang: "es",
         value: "LuxCal Web Calendar antes de 5.3.3m (versión MySQL) y antes de 5.3.3L (versión SQLite) contiene una vulnerabilidad de inyección SQL en Retrieve.php. Si se explota esta vulnerabilidad, la información en una base de datos puede eliminarse, alterarse o recuperarse.",
      },
   ],
   id: "CVE-2025-25222",
   lastModified: "2025-02-18T01:15:09.210",
   metrics: {
      cvssMetricV30: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "LOW",
               baseScore: 7.3,
               baseSeverity: "HIGH",
               confidentialityImpact: "LOW",
               integrityImpact: "LOW",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
               version: "3.0",
            },
            exploitabilityScore: 3.9,
            impactScore: 3.4,
            source: "vultures@jpcert.or.jp",
            type: "Secondary",
         },
      ],
   },
   published: "2025-02-18T01:15:09.210",
   references: [
      {
         source: "vultures@jpcert.or.jp",
         url: "https://jvn.jp/en/jp/JVN26024080/",
      },
      {
         source: "vultures@jpcert.or.jp",
         url: "https://www.luxsoft.eu/?download",
      },
      {
         source: "vultures@jpcert.or.jp",
         url: "https://www.luxsoft.eu/lcforum/viewtopic.php?pid=1984#p1984",
      },
   ],
   sourceIdentifier: "vultures@jpcert.or.jp",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-89",
            },
         ],
         source: "vultures@jpcert.or.jp",
         type: "Primary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.