pbrong hrms recruitment.go UpdateRecruitmentById cross site scripting

published 2026-01-19 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-3212

cvss: 3.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits: 0; none known

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.

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 9 mo ago (2026-01-20)

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/TheLiao233/cve/issues/1 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	4.0	5.1	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
CNA	3.1	3.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N/E:P/RL:X/RC:R
CNA	3.0	3.5	CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N/E:P/RL:X/RC:R
CNA	2.0	4.0	AV:N/AC:L/Au:S/C:N/I:P/A:N/E:POC/RL:ND/RC:UR
CNA	4.0	2.0	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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CNA	3.1	3.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
CNA	2.0	4.0	AV:N/AC:L/Au:S/C:N/I:P/A:N

Affected products

pbrong hrms

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation
CWE-94 Improper Control of Generation of Code

References

github.com /TheLiao233/cve/issues/1
exploit, issue-tracking
vuldb.com /?id.341755
vdb-entry, technical-description
vuldb.com /?ctiid.341755
signature, permissions-required
vuldb.com /?submit.736510
third-party-advisory

Sources

CVE List CVE-2026-1161
NVD CVE-2026-1161

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary