JVNDB-2025-005050

Vulnerability from jvndb - Published: 2025-05-15 18:11 - Updated:2025-05-15 18:11
Severity ?
8.6 (High) - cvssV3_0 - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Summary
Multiple vulnerabilities in a-blog cms
Details
a-blog cms provided by appleple inc. contains multiple vulnerabilities listed below.
  • Path traversal (CWE-22)
    • CVE-2025-27566
    • This is an issue with insufficient path validation in the backup feature, and exploitation requires the administrator privilege
  • Cross-site scripting (CWE-79)
    • CVE-2025-32999
    • This issue exists in a specific field in the entry editing screen, and exploitation requires contributor or higher level privileges
  • Server-side request forgery (CWE-918)
    • CVE-2025-36560
  • Improper output neutralization for logs (CWE-117)
    • CVE-2025-41429
    CVE-2025-27566, CVE-2025-32999 haidv35 (Dinh Viet Hai) reported these vulnerabilities to the developer and coordinated. After the coordination was completed, haidv35 (Dinh Viet Hai) reported the case to JPCERT/CC to notify users of the solution through JVN. CVE-2025-36560, CVE-2025-41429 vcth4nh from VCSLab of Viettel Cyber Security (Vu Chi Thanh) reported these vulnerabilities to JPCERT/CC. JPCERT/CC coordinated with the developer.
References
Impacted products
Show details on JVN DB website
To clipboard 

{
  "@rdf:about": "https://jvndb.jvn.jp/en/contents/2025/JVNDB-2025-005050.html",
  "dc:date": "2025-05-15T18:11+09:00",
  "dcterms:issued": "2025-05-15T18:11+09:00",
  "dcterms:modified": "2025-05-15T18:11+09:00",
  "description": "a-blog cms provided by appleple inc. contains multiple vulnerabilities listed below.\r\n\r\n\u003cul\u003e\r\n\u003cli\u003ePath traversal (CWE-22)\u003c/li\u003e\r\n\u003cul\u003e\r\n\u003cli\u003eCVE-2025-27566\u003c/li\u003e\r\n\u003cli\u003eThis is an issue with insufficient path validation in the backup feature, and exploitation requires the administrator privilege\u003c/li\u003e\r\n\u003c/ul\u003e\r\n\r\n\u003cli\u003eCross-site scripting (CWE-79)\u003c/li\u003e\r\n\u003cul\u003e\r\n\u003cli\u003eCVE-2025-32999\u003c/li\u003e\r\n\u003cli\u003eThis issue exists in a specific field in the entry editing screen, and exploitation requires contributor or higher level privileges\u003c/li\u003e\r\n\u003c/ul\u003e\r\n\r\n\u003cli\u003eServer-side request forgery (CWE-918)\u003c/li\u003e\r\n\u003cul\u003e\u003cli\u003eCVE-2025-36560\u003c/li\u003e\u003c/ul\u003e\r\n\r\n\u003cli\u003eImproper output neutralization for logs (CWE-117)\u003c/li\u003e\r\n\u003cul\u003e\u003cli\u003eCVE-2025-41429\u003c/li\u003e\u003c/ul\u003e\r\n\r\nCVE-2025-27566, CVE-2025-32999\r\nhaidv35 (Dinh Viet Hai) reported these vulnerabilities to the developer and coordinated. After the coordination was completed, haidv35 (Dinh Viet Hai) reported the case to JPCERT/CC to notify users of the solution through JVN.\r\n\r\nCVE-2025-36560, CVE-2025-41429\r\nvcth4nh from VCSLab of Viettel Cyber Security (Vu Chi Thanh) reported these vulnerabilities to JPCERT/CC. JPCERT/CC coordinated with the developer.",
  "link": "https://jvndb.jvn.jp/en/contents/2025/JVNDB-2025-005050.html",
  "sec:cpe": {
    "#text": "cpe:/a:appleple:a-blog_cms",
    "@product": "a-blog cms",
    "@vendor": "appleple inc.",
    "@version": "2.2"
  },
  "sec:cvss": {
    "@score": "8.6",
    "@severity": "High",
    "@type": "Base",
    "@vector": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
    "@version": "3.0"
  },
  "sec:identifier": "JVNDB-2025-005050",
  "sec:references": [
    {
      "#text": "https://jvn.jp/en/vu/JVNVU90760614/index.html",
      "@id": "JVNVU#90760614",
      "@source": "JVN"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2025-27566",
      "@id": "CVE-2025-27566",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2025-32999",
      "@id": "CVE-2025-32999",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2025-36560",
      "@id": "CVE-2025-36560",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2025-41429",
      "@id": "CVE-2025-41429",
      "@source": "CVE"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/117.html",
      "@id": "CWE-117",
      "@title": "Improper Output Neutralization for Logs(CWE-117)"
    },
    {
      "#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
      "@id": "CWE-22",
      "@title": "Path Traversal(CWE-22)"
    },
    {
      "#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
      "@id": "CWE-79",
      "@title": "Cross-site Scripting(CWE-79)"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/918.html",
      "@id": "CWE-918",
      "@title": "Server-Side Request Forgery (SSRF)(CWE-918)"
    }
  ],
  "title": "Multiple vulnerabilities in a-blog cms"
}


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.