dbcve.org
Foiaxpress Public Access LinkApplication · Opexustech

CVE-2025-54834

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to 11.12.3.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
OPEXUS FOIAXpress Public Access Link (PAL) version v11.1.0 allows an unauthenticated, remote attacker to query the /App/CreateRequest.aspx endpoint to check for the existence of valid usernames. There are no rate-limiting mechanisms in place.

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 · high confidence

OPEXUS FOIAXpress PAL v11.1.0 contains an unauthenticated username enumeration vulnerability via the /App/CreateRequest.aspx endpoint. Attackers can determine valid usernames by submitting requests without any rate limiting protection, enabling brute-force enumeration of user accounts.

MitigationImplement rate limiting on the CreateRequest.aspx endpoint and consider additional controls such as CAPTCHA or account lockout policies to prevent automated username enumeration.

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
Foiaxpress Public Access LinkApplication
Affected:>= 11.1.0, < 11.12.3.0

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if FOIAXpress PAL is installed
    Locate the FOIAXpress Public Access Link installation in your environment and confirm the product is running.
    Affected if The product Opexustech Foiaxpress Public Access Link is not present in your environment.
  2. Check the installed version
    Retrieve the installed version of FOIAXpress PAL and compare it to the affected range: >= 11.1.0 and < 11.12.3.0
    Affected if The installed version falls within the range 11.1.0 through 11.12.2.x
  3. Verify CreateRequest.aspx endpoint is accessible
    Confirm the /App/CreateRequest.aspx endpoint is exposed and reachable without authentication in your environment.
    Affected if The endpoint is publicly or internally accessible without authentication.
  4. Test for rate limiting on the endpoint
    Send multiple rapid requests to /App/CreateRequest.aspx and observe if any throttling, rate limiting, or account lockout occurs.
    Affected if No rate limiting, throttling, or account lockout is enforced on the endpoint, allowing unlimited rapid requests.

Your environment is affected if FOIAXpress PAL version 11.1.0 through 11.12.2.x is installed, the CreateRequest.aspx endpoint is accessible, and no rate limiting or account lockout protections are in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.12.3.0 or later
Fixed in 11.12.3.0
Interim mitigation

Implement rate limiting on the CreateRequest.aspx endpoint and consider additional controls such as CAPTCHA or account lockout policies to prevent automated username enumeration.

Recommended fix High confidence

11.12.3.0

  1. 1. Verify current version of FOIAXpress Public Access Link by checking the application or system information.
  2. 2. Schedule a maintenance window for the upgrade process.
  3. 3. Back up the current FOIAXpress PAL configuration and database according to organizational backup procedures.
  4. 4. Download the updated FOIAXpress PAL version 11.12.3.0 or later from the official vendor source.
  5. 5. Apply the upgrade following OPEXUS standard upgrade procedures for the PAL component.
  6. 6. Verify the upgrade was successful by checking the application version information.
  7. 7. Test the /App/CreateRequest.aspx endpoint to confirm the rate-limiting or username enumeration protection is now in place.
  8. 8. Monitor logs for any continued enumeration attempts.
Caveat Review OPEXUS release notes for 11.12.3.0 for any configuration or feature changes that may affect existing workflows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Foiaxpress Public Access Link Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54834 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54834 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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