dbcve.org
Foiaxpress Public Access LinkApplication · Opexustech

CVE-2025-54833

HIGH · 7.5 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to 11.12.3.0 or later.
See remediation →
84/100
Remediation priority · High
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 attackers to bypass account-lockout and CAPTCHA protections. Unauthenticated remote attackers can more easily brute force passwords.

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 confidence

OPEXUS FOIAXpress PAL v11.1.0 contains a security flaw allowing unauthenticated remote attackers to bypass both account-lockout policies and CAPTCHA challenges designed to prevent automated attacks. This enables malicious actors to conduct password brute-force attacks against the public access portal without triggering the intended account-lockout defenses or CAPTCHA verification.

MitigationImplement proper enforcement of account-lockout thresholds and CAPTCHA validation on every failed authentication attempt, or upgrade to a patched version if available. Consider implementing additional compensating controls such as IP-based rate limiting and multi-factor 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
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
High
Integrity
None
Availability
None

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

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

  1. Identify FOIAXpress PAL version
    Locate the installed version of Opexustech FOIAXpress Public Access Link in the application administrative interface or system documentation. Common locations include the About page, version info in the footer, or the application's configuration files.
    Affected if The installed version is 11.1.0 or higher but below 11.12.3.0
  2. Confirm public access portal is enabled
    Verify that the FOIAXpress Public Access Link (PAL) module is enabled and accessible. This is typically found in the application settings under public access or authentication configuration.
    Affected if The public access portal is enabled and exposed to network access
  3. Review account-lockout configuration
    Access the authentication security settings in the FOIAXpress admin console. Locate the account-lockout threshold configuration and verify the number of failed attempts allowed before lockout occurs.
    Affected if Account-lockout is configured but may not be properly enforced on the public portal
  4. Verify CAPTCHA enforcement status
    Check the public login page for CAPTCHA implementation. Look for CAPTCHA challenges on the authentication form or confirm through admin settings that CAPTCHA is configured for failed login attempts.
    Affected if CAPTCHA is configured but not being triggered on the public access login page
  5. Inspect authentication logs for attack patterns
    Review FOIAXpress authentication and security logs for patterns indicating repeated failed login attempts against the public portal without triggering lockout or CAPTCHA. Look for high volumes of failed attempts from single IP addresses.
    Affected if Logs show multiple failed authentication attempts from the same source that did not result in account lockout or CAPTCHA challenges

A system is affected if it runs FOIAXpress PAL version 11.1.0 through 11.12.2.x with the public access portal enabled and the observed behavior shows failed logins bypassing lockout and CAPTCHA protections.

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 proper enforcement of account-lockout thresholds and CAPTCHA validation on every failed authentication attempt, or upgrade to a patched version if available. Consider implementing additional compensating controls such as IP-based rate limiting and multi-factor authentication.

Recommended fix High confidence

11.12.3.0 or later

  1. Identify all FOIAXpress PAL instances running version 11.1.0 through 11.12.2.x
  2. Schedule a maintenance window for the upgrade procedure
  3. Perform a complete backup of the current configuration and database
  4. Upgrade FOIAXpress PAL to version 11.12.3.0 or later
  5. Verify the upgrade completed successfully by checking the version number
  6. Confirm that account-lockout and CAPTCHA protections are functioning correctly
  7. Monitor authentication logs to verify brute force protection is active

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54833 — 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-54833 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