CVE-2025-23477
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 · uneditedMissing Authorization vulnerability in realtyworkstation Realty Workstation realty-workstation allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Realty Workstation: from n/a through <= 1.0.45.
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 confidenceThis is a broken access control vulnerability in Realty Workstation version 1.0.45 and earlier where certain functionality lacks proper Authorization checks, allowing authenticated users (or potentially unauthenticated users) to access resources or perform actions outside their intended permissions. The specific endpoints or actions affected are not detailed in the advisory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
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.
-
Identify installed Realty Workstation versionLocate the application version number in the software itself (typically in Help > About, a version info file, or the installer metadata) or check the installed package via your software inventory systemAffected if The installed version is 1.0.45 or any earlier version
-
Verify access control configuration existsInspect the application configuration files or admin settings for Role-Based Access Control (RBAC) or Access Control List (ACL) settings. Look for files such as config.xml, settings.json, or database tables storing permission rulesAffected if No RBAC or ACL configuration is found, or authorization checks are disabled in the configuration
-
Test sensitive endpoint accessibilityUsing an authenticated user with limited privileges (or no authentication), attempt to access or invoke functionality that should be restricted to administrators or other roles. This includes API endpoints, administrative functions, or data access pathsAffected if Lower-privileged or unauthenticated users can access resources or execute actions intended only for higher-privileged roles
-
Review user role assignmentsExamine the user management section of the application to confirm which users are assigned to which roles, and verify that role permissions are properly enforcedAffected if Users have unintended elevated permissions or role assignments are not being enforced
A user is affected if their installed Realty Workstation version is 1.0.45 or earlier AND the application lacks proper authorization enforcement on sensitive endpoints or functions.
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.
From vendor dataImplement proper Role-Based Access Control (RBAC) or ACL checks on all sensitive endpoints and functions within the application, and upgrade to the latest patched version of Realty Workstation when available.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23477 — 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-23477 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