LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000525: openpsa contains a PHP Object Injection vulnerability in Form data passed as GET request variables that can...

openpsa contains a PHP Object Injection vulnerability in Form data passed as GET request variables that can result in Possible information disclosure and remote code execution. This attack appear to be exploitable via Specially crafted GET request variable containing serialised PHP object. This vulnerability appears to have been fixed in after commit 097eae0.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-1000525 is a PHP object injection issue in OpenPSA. A specially crafted GET request variable containing serialized PHP object data may lead to information disclosure or remote code execution. Public sources do not provide CVSS scoring, precise affected versions, or evidence of active exploitation.

Executive priority

Prioritize investigation if OpenPSA is deployed, especially on public web infrastructure. The potential impact includes remote code execution, but available public evidence is incomplete. If OpenPSA is not present, no direct exposure is indicated by these sources.

Technical view

The CVE describes PHP object injection through form data passed as GET request variables in OpenPSA. The reported impact is possible information disclosure and remote code execution. The record states the issue was fixed after commit 097eae0, but the supplied sources do not define affected version ranges.

Likely exposure

Exposure is most likely for internet-facing OpenPSA deployments running code that does not include the post-097eae0 fix. Version and package boundaries are not stated in the CVE data, so teams must verify by repository history or vendor guidance.

Exploitation context

The CVE says exploitation uses a specially crafted GET request variable containing a serialized PHP object. The provided sources do not show KEV listing or active exploitation evidence. Do not treat exploitation in the wild as confirmed from this bundle.

Researcher notes

Key gaps are missing CVSS, missing affected versions, and no named exploit-in-the-wild evidence. Validation should focus on confirming OpenPSA presence and whether the deployed code includes the post-097eae0 fix, without assuming package-version coverage not shown in the sources.

Mitigation direction

  • Identify any OpenPSA deployments and their source or package version.
  • Verify whether the code includes the fix after commit 097eae0.
  • Review the GitHub issue and vendor repository guidance for upgrade direction.
  • Restrict public access to legacy OpenPSA instances where business permits.
  • Monitor application logs for unusual serialized object-like GET parameters.

Validation and detection

  • Inventory OpenPSA hosts, including archived or internally maintained deployments.
  • Compare deployed code against the referenced fixed commit state.
  • Check web logs for suspicious GET parameters targeting form handling paths.
  • Confirm no exposed instance runs unverified legacy OpenPSA code.
  • Document uncertainty where package versions cannot be mapped to the fix.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-1000525 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.