CVE-2025-58244
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Anps Constructo constructo allows Object Injection.This issue affects Constructo: from n/a through <= 4.3.9.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in Anps Constructo CMS (versions up to 4.3.9) allows attackers to trick authenticated users into performing unintended actions that trigger PHP Object Injection. This occurs because the application lacks proper anti-CSRF tokens on state-changing operations, combined with unsafe deserialization of user-controlled input, potentially enabling remote code execution or data manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Anps Constructo CMS versionLocate the version identifier in the CMS installation, typically found in the admin dashboard under 'About' or 'System Info', or check version.php/version.txt in the web root directoryAffected if The installed version is 4.3.9 or any earlier version (versions up to 4.3.9 are affected)
-
Identify state-changing operationsReview application forms and AJAX endpoints that perform database writes, user management, content updates, or configuration changesAffected if The application lacks anti-CSRF tokens (such as hidden form fields or request headers) on these state-changing operations
-
Inspect deserialization implementationSearch the application source code for usage of PHP deserialization functions (unserialize) that process user-controlled input from request parameters, cookies, or stored dataAffected if The application uses unserialize() on data that can be influenced by users without class whitelist restrictions
-
Verify user input reaches deserializationTrace the data flow from user inputs (POST/GET parameters, cookies) to deserialization functions to confirm attacker-controlled data can reach unsafe unserialize() callsAffected if User-supplied input is passed directly to unserialize() without validation or restriction to safe classes
A user is affected if running Anps Constructo CMS version 4.3.9 or lower AND the application performs unsafe deserialization of user input on state-changing operations that lack CSRF protection.
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.
From vendor dataImplement anti-CSRF tokens on all state-changing operations and validate/sanitize all user inputs to prevent unsafe object injection. Review and restrict deserialization to whitelisted classes only.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58244 — 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-58244 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