VulnerabilityPublished 19 Jan 2026Updated 23 Feb 2026

CVE-2026-1161: pbrong hrms · Cross-site Scripting

Affects pbrong hrmsSource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 09:16 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 14% 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 19 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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
pbronghrms	Affected =1.0.1	Fixed in–
Gogithub.com/pbrong/hrms`pkg:golang/github.com/pbrong/hrms`Other threats	Affected =1.0.1	Fixed in–

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

AI-suggested

Implement strict input validation and output encoding in the UpdateRecruitmentById function to sanitize all user-supplied data, preventing malicious script injection.
Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts within the HRMS web application.
Use HTTP-only and Secure flags on session cookies to reduce the risk of cookie theft via XSS.
Educate users about the risks of clicking suspicious links or submitting untrusted input to reduce the likelihood of successful social engineering.
Monitor web application logs and user activity for unusual patterns indicative of XSS exploitation attempts.
Isolate the HRMS environment behind VPNs or internal networks where possible to limit external exposure.
Engage with the vendor or development team to obtain or develop patches addressing the root cause.
Conduct regular security assessments and penetration tests focusing on input validation and XSS vulnerabilities.
Consider deploying web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting the affected endpoints.
Maintain up-to-date backups of HRMS data to enable recovery in case of compromise.

Description

A vulnerability was detected in pbrong hrms 1.0.1. The affected element is the function UpdateRecruitmentById of the file /handler/recruitment.go. The manipulation results in cross site scripting. The attack may be launched remotely. The exploit is now public and may be used.

Impact

The primary impact of this XSS vulnerability is on the confidentiality and integrity of user sessions within the pbrong hrms application. Attackers could execute arbitrary scripts to steal session cookies, impersonate users, or manipulate displayed content, potentially leading to unauthorized access to sensitive HR data. This could result in exposure of personal employee information, recruitment data, or internal communications. While availability is not directly affected, successful exploitation could undermine user trust and lead to reputational damage. Organizations relying on pbrong hrms for recruitment and HR management may face compliance risks if sensitive data is compromised. The remote exploitability without authentication increases the attack surface, especially if the application is accessible over the internet. The requirement for user interaction somewhat limits automated exploitation but does not eliminate risk, as social engineering can facilitate triggering the payload. The absence of patches means organizations must rely on compensating controls until a fix is available. Overall, the vulnerability poses a moderate risk that could be leveraged in targeted attacks against HR departments or broader organizational networks.

References

Community reviews

Loading reviews…