dbcve.org
Corehr Core PortalApplication · Theaccessgroup

CVE-2019-25064

HIGH · 8.8 CVSS v3.1 Published 2022-06-09
Fix available
A fix is available. Upgrade to after 27.0.7 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A vulnerability was found in CoreHR Core Portal up to 27.0.7. It has been classified as problematic. Affected is an unknown function. The manipulation leads to cross site request forgery. It is possible to launch the attack remotely. Upgrading to version 27.0.8 is able to address this issue. It is recommended to upgrade the affected component.

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

Cross-site request forgery (CSRF) vulnerability in CoreHR Core Portal allows attackers to induce authenticated users to perform unintended actions. The vulnerability exists in unknown functions of the portal up to version 27.0.7. Successful exploitation could allow remote attackers to execute unauthorized commands on behalf of legitimate users.

MitigationUpgrade CoreHR Core Portal to version 27.0.8 or later to address the CSRF vulnerability. This is a straightforward version upgrade that includes the security fix.

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
Corehr Core PortalApplication
Affected:>= 27.0.0, <= 27.0.7

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Confirm CoreHR Core Portal is installed
    Locate the CoreHR installation directory or check for running services named 'CoreHR' or 'Core Portal' on the system
    Affected if The CoreHR Core Portal software is present on the system
  2. Identify the installed CoreHR version
    Check the application's about page, version file, or configuration files within the CoreHR installation directory for a version string
    Affected if The installed version is 27.0.0, 27.0.1, 27.0.2, 27.0.3, 27.0.4, 27.0.5, 27.0.6, or 27.0.7
  3. Verify CSRF protection mechanism status
    Examine the application configuration or inspect HTTP responses when performing actions in the portal to check for anti-CSRF token presence in forms and requests
    Affected if Anti-CSRF tokens are missing from portal forms and requests, indicating the vulnerable configuration is active

The environment is affected if CoreHR Core Portal is installed and running any version between 27.0.0 and 27.0.7, where CSRF protection is not properly enforced.

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 a release after 27.0.7
Interim mitigation

Upgrade CoreHR Core Portal to version 27.0.8 or later to address the CSRF vulnerability. This is a straightforward version upgrade that includes the security fix.

Recommended fix High confidence

CoreHR Core Portal version 27.0.8

  1. 1. Back up the current CoreHR Core Portal installation and database before proceeding with the upgrade.
  2. 2. Obtain CoreHR Core Portal version 27.0.8 from the official CoreHR vendor or authorized distribution channel.
  3. 3. Follow the vendor's documented upgrade procedure to install version 27.0.8, ensuring all pre-upgrade requirements are met.
  4. 4. After installation, verify the application is running correctly and test that CSRF protection is functioning as expected.
  5. 5. Confirm the version upgrade was successful by checking the application version information.

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

Fix this in Corehr Core Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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