CVE-2025-58462
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 · uneditedOPEXUS FOIAXpress Public Access Link (PAL) before version 11.13.1.0 allows SQL injection via SearchPopularDocs.aspx. A remote, unauthenticated attacker could read, write, or delete any content in the underlying database.
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 confidenceOPEXUS FOIAXpress Public Access Link (PAL) versions before 11.13.1.0 contain an unauthenticated SQL injection vulnerability in the SearchPopularDocs.aspx page. A remote attacker can exploit this flaw to execute arbitrary SQL queries against the underlying database, enabling complete data exfiltration, modification, or deletion.
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< 11.13.1.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate FOIAXpress PAL installationCheck IIS Manager for websites or applications named FOIAXpress or FOIAXpress PAL. Common installation paths are C:\inetpub\wwwroot\FOIAXpress or under the default website in IIS. Look for the web.config file in the application root.Affected if No FOIAXpress PAL installation found on the server
-
Determine installed FOIAXpress PAL versionCheck the version of the FOIAXpress PAL installation. Examine the assembly version of DLLs in the /bin folder, look for a version.txt or version.info file in the installation directory, or check the application's About page if accessible through the web interface. Compare the version number to 11.13.1.0.Affected if Installed version is below 11.13.1.0
-
Verify SearchPopularDocs.aspx existsLocate the SearchPopularDocs.aspx file within the FOIAXpress PAL web directory structure. Search in the web root and common subdirectories like /Search or /Pages. Confirm the file exists on the file system.Affected if SearchPopularDocs.aspx file is present in the installation
-
Check if SearchPopularDocs.aspx is externally accessibleAttempt to access the SearchPopularDocs.aspx page via HTTP/HTTPS without providing credentials. Use a browser or curl command against the URL (for example, https://yourserver/SearchPopularDocs.aspx or the appropriate path). Verify if the page loads or returns an error versus redirecting to a login page.Affected if The page loads or returns application content without requiring authentication
The environment is affected if FOIAXpress PAL version is lower than 11.13.1.0 and the SearchPopularDocs.aspx page is accessible without authentication.
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 · scoped11.13.1.0
Upgrade FOIAXpress PAL to version 11.13.1.0 or later to obtain the patched build. Until patched, consider disabling the affected SearchPopularDocs.aspx endpoint or placing it behind a web application firewall.
11.13.1.0
- Identify the current installed version of FOIAXpress Public Access Link (PAL) in your environment
- Contact OPEXUS support or consult official documentation to obtain the version 11.13.1.0 upgrade package
- Review upgrade documentation for any pre-requisites or migration steps
- Apply the upgrade in a test/staging environment first to validate
- Deploy version 11.13.1.0 to production environment
- Verify the SQL injection vulnerability is remediated by testing the SearchPopularDocs.aspx endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58462 — 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-58462 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