In Liferay Portal before 7.3.1, Liferay Portal 6.2 EE, and Liferay DXP 7.2, DXP 7.1 and DXP 7.0, the property 'portlet.resource.id.banned.pa
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 67.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: com.liferay.portal:com.liferay.portal.impl (Maven) 7.4.0, 7.1.3; com.liferay.portal:release.dxp.bom (Maven) 7.1.10.fp19, 7.2.10.fp7, 7.0.10.fp93; com.liferay.portal:release.portal.bom (Maven) 7.3.1.
Low priority for now. Upgrade to com.liferay.portal:com.liferay.portal.impl (Maven) 7.4.0, 7.1.3; com.liferay.portal:release.dxp.bom (Maven) 7.1.10.fp19, 7.2.10.fp7, 7.0.10.fp93; com.liferay.portal:release.portal.bom (Maven) 7.3.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
In Liferay Portal before 7.3.1, Liferay Portal 6.2 EE, and Liferay DXP 7.2, DXP 7.1 and DXP 7.0, the property 'portlet.resource.id.banned.paths.regexp' can be bypassed with doubled encoded URLs.
- Published
- Sep 24, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.2% · 68th percentile
- CWE
- —
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| liferay | digital experience platform | cpe:2.3:a:liferay:digital_experience_platform |
| liferay | liferay portal | cpe:2.3:a:liferay:liferay_portal |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- liferay digital experience platform7.0
- liferay digital experience platform7.1
- liferay digital experience platform7.2
- liferay liferay portalbefore 7.3.1
- liferay liferay portal6.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | com.liferay.portal:com.liferay.portal.impl | from 7.2.0 · before 7.4.0 | 7.4.0 |
| Maven | com.liferay.portal:com.liferay.portal.impl | before 7.1.3 | 7.1.3 |
| Maven | com.liferay.portal:release.dxp.bom | from 7.1.0 · before 7.1.10.fp19 | 7.1.10.fp19 |
| Maven | com.liferay.portal:release.dxp.bom | from 7.2.0 · before 7.2.10.fp7 | 7.2.10.fp7 |
| Maven | com.liferay.portal:release.dxp.bom | before 7.0.10.fp93 | 7.0.10.fp93 |
| Maven | com.liferay.portal:release.portal.bom | before 7.3.1 | 7.3.1 |
Same product
liferay: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-38002The workflow component in Liferay Portal 7.3.2 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, 35Monitor
- CVE-2024-26273Cross-site request forgery (CSRF) vulnerability in the content page editor in Liferay Portal 7.4.0 through 7.4.3.103, and Liferay DXP 2023.Q35Monitor
- CVE-2024-26272Cross-site request forgery (CSRF) vulnerability in the content page editor in Liferay Portal 7.3.2 through 7.4.3.107, and Liferay DXP 2023.Q35Monitor
- CVE-2024-26271Cross-site request forgery (CSRF) vulnerability in the My Account widget in Liferay Portal 7.4.3.75 through 7.4.3.111, and Liferay DXP 2023.35Monitor
- CVE-2020-15841Liferay Portal before 7.3.0, and Liferay DXP 7.0 before fix pack 89, 7.1 before fix pack 17, and 7.2 before fix pack 4, does not safely test35Monitor
- CVE-2025-3594Path traversal vulnerability with the downloading and installation of Xuggler in Liferay Portal 7.0.0 through 7.4.3.4, and Liferay DXP 7.4 G34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:com.liferay.portal:com.liferay.portal.impl | 7.1.3 | Package registry (OSV) |
| Maven:com.liferay.portal:com.liferay.portal.impl | 7.4.0 | Package registry (OSV) |
| Maven:com.liferay.portal:release.dxp.bom | 7.0.10.fp93 | Package registry (OSV) |
| Maven:com.liferay.portal:release.dxp.bom | 7.1.10.fp19 | Package registry (OSV) |
| Maven:com.liferay.portal:release.dxp.bom | 7.2.10.fp7 | Package registry (OSV) |
| Maven:com.liferay.portal:release.portal.bom | 7.3.1 | Package registry (OSV) |
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
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.