CVE-2025-13181VulnerabilityPublished 14 Nov 2025Updated 24 Feb 2026

CVE-2025-13181: pojoin h3blog · Cross Site Scripting

Affects pojoin h3blogSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubpojoin/h3blog`pkg:github/pojoin/h3blog`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should include restricting access to the /admin/cms/material/add endpoint via network controls such as IP whitelisting or VPN-only access to limit exposure to trusted administrators. 2. Implement web application firewall (WAF) rules to detect and block suspicious input patterns targeting the 'Name' parameter, focusing on script tags or typical XSS payloads. 3. Educate administrative users to avoid clicking on untrusted links or visiting suspicious pages while logged into the administrative interface. 4. Conduct input validation and output encoding on the 'Name' parameter server-side to neutralize malicious scripts, if possible, as a temporary patch. 5. Monitor logs for unusual activity or repeated attempts to access the vulnerable endpoint with suspicious parameters. 6. Engage with the vendor or community to obtain or develop an official patch addressing the vulnerability. 7. Consider deploying Content Security Policy (CSP) headers to restrict script execution sources, reducing the impact of potential XSS payloads. 8. Regularly update and audit the CMS and its components to detect and remediate similar vulnerabilities proactively.

Description

A vulnerability was determined in pojoin h3blog 1.0. The affected element is an unknown function of the file /admin/cms/material/add. Executing a manipulation of the argument Name can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized.

Impact

The primary impact of CVE-2025-13181 is on the confidentiality and integrity of administrative sessions within pojoin h3blog 1.0. Successful exploitation could allow attackers to execute arbitrary scripts in the context of an administrator's browser, potentially leading to session hijacking, theft of sensitive information, or unauthorized administrative actions such as content manipulation or configuration changes. While availability impact is minimal, the compromise of administrative control could indirectly affect site availability or trustworthiness. The vulnerability's remote exploitability without authentication increases the attack surface, especially if administrative users access the vulnerable interface from untrusted networks. Organizations relying on pojoin h3blog for content management may face reputational damage, data breaches, or compliance issues if exploited. The lack of known exploits in the wild currently limits immediate widespread impact, but public disclosure raises the likelihood of future attacks.

Summary

CVE-2025-13181 is a cross-site scripting vulnerability identified in pojoin h3blog version 1.0, specifically within an unknown function of the /admin/cms/material/add endpoint. The vulnerability arises from improper sanitization or validation of the 'Name' parameter, which can be manipulated by an attacker to inject malicious JavaScript code. This injection occurs in a context that allows the execution of arbitrary scripts when an administrative user accesses the affected page or functionality. The attack vector is remote and does not require prior authentication, although user interaction is necessary for the payload to execute, such as an admin clicking a malicious link or viewing a crafted page. The CVSS 4.0 score of 5.1 reflects medium severity, considering the ease of exploitation (low complexity), no privileges required, but user interaction needed. The impact primarily affects confidentiality and integrity by potentially allowing session hijacking, defacement, or unauthorized actions within the administrative interface. No patches or fixes have been linked yet, and no known exploits are reported in the wild, but public disclosure increases the risk of exploitation attempts. Organizations using pojoin h3blog 1.0 should be aware of this vulnerability and monitor for suspicious activity or consider temporary mitigations until an official patch is released.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:21 UTC

Technical details

References

Community reviews

Related threats