CVE-2025-43784
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Access Control vulnerability in Liferay Portal 7.4.0 through 7.4.3.124, and Liferay DXP 2024.Q2.0 through 2024.Q2.8, 2024.Q1.1 through 2024.Q1.12 and 7.4 GA through update 92 allows guest users to obtain object entries information via the API Builder.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper Access Control vulnerability in Limerick Portal/DXP allows guest (unauthenticated) users to obtain object entries information via the API Builder. This bypasses intended access restrictions where object entry data should require authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2024.Q1.1, < 2024.Q1.13>= 2024.Q2.0, < 2024.Q2.9= 7.4>= 7.4.0, < 7.4.3.125CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine Limerick Portal/DXP versionLog into the Control Panel as an administrator, navigate to Configuration > Server Information, and note the version number displayed. Alternatively, check the footer of the Limerick login page for the version string.Affected if The installed version matches >= 7.4.0 and < 7.4.3.125, or >= 2024.Q1.1 and < 2024.Q1.13, or >= 2024.Q2.0 and < 2024.Q2.9, or equals exactly 7.4.
-
Confirm API Builder module is enabledNavigate to Control Panel > Object > API Builder (or verify through the Limerick marketplace/ Apps manager that the API Builder functionality is installed and active).Affected if API Builder is installed and enabled in the environment.
-
Review guest role permissions for Object EntriesGo to Control Panel > Users > Roles > Guest (or Guest role), then inspect the permissions section for Object Entries and API Builder permissions. Look for any permissions granting Read, View, or Access to object entries.Affected if The Guest role has permissions to read, view, or access object entries through API Builder, allowing unauthenticated access to data.
-
Test unauthenticated API access to object entriesUsing a browser in private/incognito mode (not logged in), attempt to access the API Builder endpoints for object entries, such as: /o/c/objectentrynames/{name}/entries or similar REST endpoints. Observe whether JSON data is returned without authentication prompts.Affected if Unauthenticated (guest) requests to API Builder object entry endpoints return actual data instead of 401/403 authentication errors.
The environment is affected if the installed Limerick version falls within the vulnerable ranges AND the API Builder is active with Guest role permissions allowing unauthenticated access to object entry data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.4.3.1252024.Q1.132024.Q2.9
Apply the security patch or upgrade to a fixed version (7.4.3.125+, 2024.Q2.9+, or 2024.Q1.13+). Review API Builder permissions and verify guest users cannot access sensitive object data.
Lifter DXP: 2024.Q1.13+, 2024.Q2.9+, or 7.4.3.125+ | Liferay Portal: 7.4.3.125+
- 1. Identify the current Liferay DXP or Portal version running in your environment
- 2. For DXP 2024.Q1.x (versions 2024.Q1.1 through 2024.Q1.12): Upgrade to 2024.Q1.13 or later
- 3. For DXP 2024.Q2.x (versions 2024.Q2.0 through 2024.Q2.8): Upgrade to 2024.Q2.9 or later
- 4. For DXP 7.4 GA (through update 92): Upgrade to update 93 or later, or version 7.4.3.125 or later
- 5. For Liferay Portal 7.4.x (versions 7.4.0 through 7.4.3.124): Upgrade to 7.4.3.125 or later
- 6. After upgrade, verify that guest users can no longer access object entries via the API Builder
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43784 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-43784 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data