A potential security vulnerability has been identified with certain HP printers and MFPs in 2405129_000052 and other firmware versions.
A potential security vulnerability has been identified with certain HP printers and MFPs in 2405129_000052 and other firmware versions. This vulnerability is known as Cross Site Request Forgery, and could potentially be exploited remotely to allow elevation of privilege.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Oct 3, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-352
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| hp | m0p39a | cpe:2.3:h:hp:m0p39a |
| hp | f2a70a firmware | cpe:2.3:o:hp:f2a70a_firmware |
| hp | f2a70a | cpe:2.3:h:hp:f2a70a |
| hp | f2a71a firmware | cpe:2.3:o:hp:f2a71a_firmware |
| hp | f2a71a | cpe:2.3:h:hp:f2a71a |
| hp | f2a67a firmware | cpe:2.3:o:hp:f2a67a_firmware |
| hp | f2a67a | cpe:2.3:h:hp:f2a67a |
| hp | b5l26a firmware | cpe:2.3:o:hp:b5l26a_firmware |
| hp | b5l26a | cpe:2.3:h:hp:b5l26a |
| hp | b5l39a firmware | cpe:2.3:o:hp:b5l39a_firmware |
| hp | b5l39a | cpe:2.3:h:hp:b5l39a |
| hp | c2s11a firmware | cpe:2.3:o:hp:c2s11a_firmware |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hp a2w75a firmwarebefore 2405129_000054
- hp a2w76a firmwarebefore 2405129_000054
- hp a2w77a firmwarebefore 2405129_000057
- hp a2w78a firmwarebefore 2405129_000057
- hp a2w79a firmwarebefore 2405129_000057
- hp b3g84a firmwarebefore 2405129_000040
- hp b3g85a firmwarebefore 2405129_000040
- hp b3g86a firmwarebefore 2405129_000040
- hp b5l04a firmwarebefore 2405129_000050
- hp b5l05a firmwarebefore 2405129_000050
- hp b5l06a firmwarebefore 2405129_000050
- hp b5l07a firmwarebefore 2405129_000050
- hp b5l26a firmwarebefore 2405129_000056
- hp b5l39a firmwarebefore 2405129_000056
- hp b5l46a firmwarebefore 2405129_000038
- hp b5l47a firmwarebefore 2405129_000038
- hp b5l48a firmwarebefore 2405129_000038
- hp b5l49a firmwarebefore 2405129_000038
- hp b5l50a firmwarebefore 2405129_000038
- hp b5l54a firmwarebefore 2405129_000038
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hp). Independent of NVD's CPE analysis and usually ahead of it.
HP Inc. Certain HP Enterprise Printers, HP PageWide Printers, and MFP Products
- 2405129_000052 and other firmware versionsaffected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.