CVE
Barn2 Document Library Pro remote code execution risk via PHP object injection
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 4.2.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.2.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.31% · 24th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
The Document Library Pro plugin for WordPress, made by Barn2 Plugins, contains a PHP object injection flaw caused by unsafe handling of serialized data. An attacker can reach it remotely, without logging in, and exploiting it could let them run code or otherwise affect the site.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
Deserialization of Untrusted Data vulnerability in Barn2 Plugins Document Library Pro document-library-pro allows Object Injection.This issue affects Document Library Pro: from n/a before 4.2.2.
Who should check
Sites and teams running the Barn2 Plugins Document Library Pro WordPress plugin before version 4.2.2
“WordPress Document Library Pro Plugin < 4.2.2 is vulnerable”
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.2.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-122662 (WordPress Document Library Pro plugin < 4.2.2 - PHP Object Injection vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-122662 (entry last updated 2026-11-16):
Affected:
- Barn2 Plugins Document Library Pro: fixed in 4.2.2
Fixed versions: 4.2.2.
Conditions (all must be true for the bug to be hit):
- Document Library Pro WordPress plugin version before 4.2.2 (source: https://patchstack.com/database/wordpress/plugin/document-library-pro/vulnerability/wordpress-document-library-pro-plugin-4-2-2-php-object-injection-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-122662 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-122662 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/document-library-pro/vulnerability/wordpress-document-library-pro-plugin-4-2-2-php-object-injection-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-122662
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-122662"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now1 day
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- document-library-pro
fixed in 4.2.2
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122662
Is CVE-2026-122662 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The plugin does not safely handle serialized PHP data, which is a PHP Object Injection flaw. According to the checked facts, an attacker can manipulate how the site processes data to run harmful actions on the server.Source: patchstack.com
Which versions are affected by CVE-2026-122662?
document-library-pro: before 4.2.2.Source: cve.now feed data
Am I affected, and how do I check?
Document Library Pro WordPress plugin versions before 4.2.2 are affected. To check a site, look at the plugin version shown on the WordPress Plugins screen or in the plugin's header in the plugins folder.Source: patchstack.com
How do I fix CVE-2026-122662?
Update the Document Library Pro plugin to version 4.2.2 or later, which the advisory names as the fix.Source: patchstack.com